CVE-2022-25679
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 · uneditedDenial of service in video due to improper access control in broadcast receivers in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
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 confidenceThis vulnerability in Qualcomm Snapdragon processors allows denial of service in video functionality due to improper access control in broadcast receivers. The flaw enables a local attacker to send specially crafted broadcasts that can disrupt video services, potentially causing device instability or service interruption.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 model in the deviceOn Android devices, go to Settings > About Phone > SIM Status or use terminal command 'getprop ro.product.board' or 'cat /proc/cpuinfo' to identify the chipset modelAffected if The chipset model matches one of: Aqt1000, Qca6390, Qca6391, Qca6420, Qca6430, Qcm2290, Qcm4290, or Qcm6490
-
Check the baseband or firmware versionOn Android, go to Settings > About Phone > Baseband version or use 'getprop gsm.version.baseband' in terminal. For other devices, consult vendor documentation for firmware version lookupAffected if The firmware version corresponds to an affected chipset listed in the CVE and has not been patched
-
Verify the Android security patch levelGo to Settings > About Phone > Android security patch level or use 'getprop ro.build.version.security_patch' in terminalAffected if The security patch level is earlier than the vendor-supplied patch date for this CVE (typically March 2022 or later depending on OEM)
-
Check if video broadcast receivers are accessibleUse a security scanning tool or review app permissions to list broadcast receivers registered by video-related services. On Android, use 'dumpsys package' to list receiversAffected if Video services expose unprotected broadcast receivers that accept external intents without proper permission checks
A device is affected if it contains any of the listed Qualcomm chipsets (Aqt1000, Qca6390, Qca6391, Qca6420, Qca6430, Qcm2290, Qcm4290, Qcm6490) and the vendor security patch for CVE-2022-25679 has not been applied.
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 security patches from device manufacturers. This is a chipset-level vulnerability requiring firmware updates from Qualcomm and subsequent OTA updates from device OEMs.
- Consultation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25679 — 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-25679 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