CVE-2025-47390
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 while preprocessing IOCTL request in JPEG driver.
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 confidenceMemory corruption vulnerability exists in the JPEG driver's IOCTL request preprocessing logic. This indicates improper input validation or buffer handling when processing IOCTL (I/O Control) commands sent to the JPEG driver, allowing an attacker to corrupt memory and potentially escalate privileges or cause denial of service.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 the Qualcomm SoC or platform in your environmentCheck system information, device specs, or firmware binaries to determine which Qualcomm chip/platform is in use. Look for model numbers: Qcm5430, Qcm6490, Sc8380xp, Snapdragon 7c+ Gen 3, Snapdragon 8cx Gen 3, Wcd9370, Wcd9375, or Vc3 Platform.Affected if The system uses any of the listed Qualcomm components (Qcm5430, Qcm6490, Sc8380xp, Snapdragon 7c+ Gen 3, Snapdragon 8cx Gen 3, Wcd9370, Wcd9375, or Vc3 Platform)
-
Confirm the JPEG driver is presentExamine the firmware image or running system for the JPEG driver module. In Linux/Android environments, look for kernel modules or firmware blobs related to JPEG encoding/decoding. Check for files containing 'jpeg', 'jpg', or video/graphics driver components in the firmware filesystem.Affected if The JPEG driver module exists in the firmware or is loaded in the operating system
-
Verify IOCTL interface is exposedCheck if the JPEG driver exposes an IOCTL interface. On Linux, examine /dev/video* nodes or device files associated with the video/graphics subsystem. Look for IOCTL command handlers in the driver code or kernel modules. Verify whether user-space applications can send IOCTL requests to the driver.Affected if The JPEG driver accepts IOCTL requests from user-space or kernel-mode components
-
Check for unpatched firmware versionRetrieve the firmware version string from the device or system. Compare against vendor security advisories. Since all listed firmware versions are affected, any unpatched installation of these Qualcomm components is vulnerable.Affected if The firmware version has not been patched by the vendor and matches an affected product
Your environment is affected if you are running any of the listed Qualcomm platforms (Qcm5430, Qcm6490, Sc8380xp, Snapdragon 7c+ Gen 3, Snapdragon 8cx Gen 3, Wcd9370, Wcd9375, or Vc3) with an unpatched firmware version that includes the JPEG driver with IOCTL interface enabled.
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 vendor-provided patches for the affected JPEG driver; prioritize patching given the high severity and memory corruption nature. If no patch available, restrict access to the affected driver or consider compensating controls.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47390 — 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-47390 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