CVE-2024-32917
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn pl330_dma_from_peri_start() of fp_spi_dma.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer overflow vulnerability exists in the pl330 DMA driver's pl330_dma_from_peri_start() function in fp_spi_dma.c, where a missing bounds check allows out-of-bounds writes during DMA operations from peripheral to memory. This memory corruption issue can be exploited for local privilege escalation without requiring user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify pl330 DMA driver presenceCheck /proc/modules or lsmod for pl330 driver loaded. On Android, also check /sys/module/pl330* or kernel boot logs for 'pl330' mentions.Affected if The pl330 DMA driver is loaded or compiled into the kernel
-
Confirm SPI DMA functionality is in useExamine kernel config for CONFIG_SPI_DMA=y or check device tree for spi dma-channel/dma-names properties. Look at /sys/class/spi* for active SPI devices using DMA.Affected if SPI DMA transfers are enabled and actively used by any SPI peripheral
-
Check kernel version for fix presenceRun 'uname -r' or check /proc/version to obtain kernel version. Compare against vendor security bulletins for CVE-2024-32917 patched kernel versions.Affected if Running an unpatched Android kernel version without the pl330 bounds check fix
-
Verify vulnerable function existsCheck /sys/module/pl330/version or examine /proc/kallsyms for pl330_dma_from_peri_start symbol. If the driver is loaded without the patch, this function handles unbounded DMA operations.Affected if The pl330_dma_from_peri_start function in fp_spi_dma.c lacks proper bounds validation
A device is affected if it runs any unpatched Android kernel version with the pl330 DMA driver loaded and SPI DMA transfers enabled, allowing the vulnerable pl330_dma_from_peri_start function to perform unbounded peripheral-to-memory DMA operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided patch for this vulnerability which adds proper bounds checking in the pl330 DMA driver. If no patch is available, consider disabling SPI DMA transfers or upgrading to a kernel version containing the fix.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32917 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32917 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data