CVE-2025-47387
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 processing IOCTLs for JPEG data without verification.
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 driver or kernel component processes IOCTL requests containing JPEG image data without validating the size, format, or contents of the data first. This allows an attacker to send specially crafted IOCTL requests with malformed JPEG data that can corrupt memory, potentially leading to code execution or 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 Qualcomm wireless componentsRun commands such as 'lspci -v' or 'lsusb' to list installed wireless adapters, or check system information for Qualcomm Aqt1000, Fastconnect, Qca6391, or Qca6420 modulesAffected if Any of the listed Qualcomm firmware components (Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, Qca6420) are present in the system
-
Determine firmware version of Qualcomm componentUse vendor-specific tools (such as 'iw list', 'ath11k-firmware-reader', or firmware analysis tools) to query the installed firmware version of the identified Qualcomm componentAffected if The firmware version matches any of the affected products (all versions of the listed products are affected)
-
Verify JPEG IOCTL handler presenceExamine driver or kernel module files for IOCTL handlers that process JPEG image data (search for IOCTL code definitions handling JPEG or image data)Affected if An IOCTL handler exists that accepts JPEG data without validated size or format checks
-
Check IOCTL interface accessibilityReview system permissions and access controls for the IOCTL interface; determine if unprivileged users or external attackers can send requests to the JPEG-handling IOCTLAffected if The IOCTL interface is exposed and accessible without sufficient privilege restrictions or authentication
-
Monitor for malformed JPEG IOCTL requestsEnable kernel debugging or driver logging; inspect system or kernel logs for any IOCTL requests containing JPEG data that trigger errors, crashes, or memory corruption indicatorsAffected if Any malformed JPEG IOCTL requests are being processed by the driver, indicating the vulnerability is being triggered
If any Qualcomm Aqt1000, Fastconnect, or Qca firmware component with an exposed JPEG-processing IOCTL handler is present, the system is likely affected since all versions of these products are vulnerable.
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 comprehensive input validation and bounds checking for all JPEG data received through IOCTL handlers. Verify data size, validate JPEG structure integrity, and ensure proper memory allocation before processing.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $11,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47387 — 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-47387 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