CVE-2025-47406
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 · uneditedInformation Disclosure while processing IOCTL handler callbacks without verifying buffer size.
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 size validation vulnerability exists in an IOCTL handler callback where the driver fails to verify the size of the input/output buffer before processing. This allows an attacker with local access to trigger an information disclosure through reading uninitialized kernel memory contents by sending specially crafted IOCTL requests with mismatched buffer sizes.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the Qualcomm firmware componentLocate the firmware version on the system by checking the boot logs, firmware partitions, or system information files. For embedded devices, examine /proc/version, dmesg output, or vendor-specific firmware metadata.Affected if The system uses any of the affected firmware identifiers: X2000086, X2000090, X2000092, X2000094, Xg101002, Xg101032, Xg101039, or X2000077.
-
Verify the exact firmware version stringExtract the full firmware version string from the system's Qualcomm component using vendor-provided tools, firmware metadata files, or by querying the device management interface.Affected if The firmware version matches any of the listed affected products (all versions are affected).
-
Confirm IOCTL handler is accessibleCheck if the driver exposing the IOCTL interface is loaded and the device node or interface is accessible on the local system. Verify local access privileges exist.Affected if The IOCTL handler interface is present and accessible to local users.
-
Inspect IOCTL handler behaviorIf possible, examine the driver code or send test IOCTL requests with mismatched buffer sizes to observe if uninitialized memory is returned.Affected if The IOCTL handler returns uninitialized kernel memory contents when buffer size does not match expected dimensions.
A system is affected if it runs any of the listed Qualcomm firmware versions and has the vulnerable IOCTL handler accessible for local access, enabling disclosure of uninitialized kernel memory through mismatched buffer size requests.
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 proper buffer size validation in the affected IOCTL handler to ensure buffer sizes match expected dimensions before processing, and zero-initialize any buffers used for returning data to prevent disclosure of kernel memory contents.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47406 — 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-47406 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