CVE-2022-25665
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 due to buffer over read in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile
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 confidenceBuffer over-read vulnerability in the kernel of Qualcomm Snapdragon chipsets (Auto, Compute, Consumer IOT, Mobile) allows unauthorized information disclosure. The CVSS 7.1 score indicates high-severity potential for exposing sensitive kernel memory contents.
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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 chipset or firmware modelCheck the device hardware specifications, system information, or bootloader/firmware inventory to determine the exact Qualcomm product model (e.g., Aqt1000, Qca6390, Ar8035)Affected if The detected model matches any of these: Aqt1000, Ar8035, Qam8295p, Qca6174a, Qca6310, Qca6335, Qca6390, Qca6391
-
Determine the firmware versionQuery the device firmware or system diagnostics for the installed version number of the identified Qualcomm productAffected if Any version is installed, since the advisory states all versions of each listed product are affected
-
Confirm the component is the kernel firmwareVerify that the identified firmware is the kernel firmware component, as the vulnerability exists in the kernel portion of the Snapdragon chipsetAffected if The vulnerability is in the kernel; non-kernel firmware components may not be affected by this specific CVE
-
Check for kernel memory access exposureReview system logs, memory dumps, or security event records for any indicators of unauthorized kernel memory reads or buffer over-read anomaliesAffected if Any evidence of kernel memory content leakage or unexpected memory read operations is observed
If the device uses any of the listed Qualcomm firmware products (Aqt1000, Ar8035, Qam8295p, Qca6174a, Qca6310, Qca6335, Qca6390, Qca6391) in its kernel component, it is affected since all versions contain the buffer over-read vulnerability.
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-supplied kernel/firmware patches from Qualcomm for affected Snapdragon platforms; customers must obtain and deploy OTA or firmware updates from their device manufacturers.
- Consultation6.0 h
- Implementation2.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 $4,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25665 — 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-2022-25665 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