CVE-2025-47372
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 · uneditedMemory Corruption when a corrupted ELF image with an oversized file size is read into a buffer without authentication.
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 ELF image parsing logic. When a corrupted ELF file with an oversized file size header is processed, the size value is used directly to allocate or read data into a buffer without proper validation. This causes memory corruption that could allow remote attackers to execute arbitrary code.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 firmware model and versionCheck the system firmware version by examining /proc/version, boot logs, or Qualcomm-specific files such as /etc/firmware_version, /sys/firmware/devicetree/base/model, or running 'cat /proc/cpuinfo' on embedded devicesAffected if The detected model is one of: Qam8255p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6595, or Qca6595au - all versions of these models are affected
-
Confirm ELF processing capabilityIdentify if the firmware includes ELF loading functionality by checking for ELF-related libraries, modules, or services in the firmware image - look for files containing 'elf' in the name or examine startup scripts for ELF parsing operationsAffected if The device firmware includes ELF image loading or parsing capabilities, which is the attack surface for this vulnerability
-
Inspect ELF loader implementationIf you have access to the firmware binary or source, examine the ELF loading code for bounds checking - search for file read operations (read, fread, recv) that handle ELF headers without prior size validation against a fixed bufferAffected if The ELF loading code performs file reads into fixed-size buffers without validating that the ELF file size does not exceed the buffer capacity before the read operation
A system is affected if it runs any of the listed Qualcomm firmware variants (Qam8255p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6595, Qca6595au) and processes ELF images through the vulnerable loader that lacks bounds checking on file size before reading into a fixed buffer.
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 dataImplement strict validation of ELF file size headers against actual buffer allocations before reading file data, and add bounds checking to prevent overflow conditions when processing ELF images.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47372 — 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-2025-47372 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