CVE-2022-25660
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 due to double free issue in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial 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 confidenceA double free memory corruption vulnerability exists in the kernel of Qualcomm Snapdragon chips across Auto, Compute, Consumer IOT, Industrial IOT, and Mobile product lines. This local privilege escalation flaw allows attackers to corrupt memory via improper memory deallocation, potentially achieving code execution with kernel privileges.
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 Snapdragon chipset in useCheck /proc/cpuinfo, /sys/class/socinfo, or run 'dmesg | grep -i snapdragon' or 'lspci | grep -i qualcomm' to determine if the device uses a Qualcomm Snapdragon processorAffected if The device does not contain a Qualcomm Snapdragon chipset - you are not affected
-
Identify specific Qualcomm firmware componentCheck firmware version via 'cat /sys/firmware/devicetree/base/model' or 'cat /proc/device-tree/model', or inspect bootloader/UEFI firmware information for the specific Qualcomm component (Aqt1000, Ar8035, Qam8295p, Qca6174a, Qca6310, Qca6335, Qca6390, or Qca6391)Affected if The firmware component matches any of the eight listed affected products (Aqt1000, Ar8035, Qam8295p, Qca6174a, Qca6310, Qca6335, Qca6390, Qca6391) - proceed to next check
-
Verify firmware version is vulnerableSince all firmware versions of the affected components are vulnerable per the CVE, confirm the exact firmware version string reported in the previous step corresponds to one of the listed affected productsAffected if The identified firmware matches any of: Aqt1000 Firmware, Ar8035 Firmware, Qam8295p Firmware, Qca6174a Firmware, Qca6310 Firmware, Qca6335 Firmware, Qca6390 Firmware, or Qca6391 Firmware - the environment is affected
If the device runs any version of the listed Qualcomm firmware components, the double free vulnerability is present and the system is affected.
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 Qualcomm firmware/security patches for affected Snapdragon components; coordinate with device OEMs for downstream patch deployment to end-user devices.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25660 — 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-25660 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