dbcve.org
Apq8053 FirmwareOperating system · Qualcomm

CVE-2022-25696

HIGH · 7.0 CVSS v3.1 Published 2022-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

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 · unedited
Memory corruption in display due to time-of-check time-of-use race condition during map or unmap in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, 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 confidence

A time-of-check time-of-use (TOCTOU) race condition exists in the display component of Qualcomm Snapdragon chips. During map or unmap operations, the vulnerability allows an attacker to potentially manipulate memory state between the time of validation and actual use, leading to memory corruption in the display subsystem.

MitigationApply vendor-provided patches from Qualcomm and downstream device manufacturers. This is a firmware-level issue requiring updates to the display driver/hardware abstraction layer; no end-user configuration remediation is available.

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 data
Apq8053 FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6420 FirmwareOperating system
Affected:all versions
Qca6430 FirmwareOperating system
Affected:all versions
Qca6574 FirmwareOperating system
Affected:all versions

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm Snapdragon chip model in your device
    Check the system-on-chip (SoC) information via /proc/cpuinfo, device tree files, or system information utilities (e.g., 'lscpu', 'cat /proc/device-tree/model', or manufacturer documentation)
    Affected if The chip model matches one of: Apq8053, Aqt1000, Msm8953, Qca6390, Qca6391, Qca6420, Qca6430, or Qca6574
  2. Verify the display subsystem is active
    Check if the display driver or display hardware component is loaded/enabled. On Linux systems, examine loaded kernel modules related to display (e.g., 'lsmod', 'dmesg | grep -i display'), or check device status in /dev or /sys for display-related components
    Affected if The display subsystem or display driver is loaded and operational on the device
  3. Check display firmware version if accessible
    Retrieve the display component firmware version through vendor-specific tools, debug interfaces, or by examining firmware files in /vendor/firmware, /lib/firmware, or through 'cat /sys/class/drm/*/version' if available on your platform
    Affected if The display firmware version cannot be determined or is confirmed to be an unpatched version (compare against any vendor-released patch versions for this CVE)
  4. Review vendor security advisories
    Check Qualcomm's security bulletins or your device manufacturer's security advisory page for references to CVE-2022-25696 and confirm whether your specific firmware version is addressed
    Affected if No patch has been applied by the device/vendor and your chip model is on the affected list

You are affected if your device uses any of the listed Qualcomm chip models (Apq8053, Aqt1000, Msm8953, Qca6390, Qca6391, Qca6420, Qca6430, Qca6574) and the display subsystem is active, and the vendor has not released a firmware patch for this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches from Qualcomm and downstream device manufacturers. This is a firmware-level issue requiring updates to the display driver/hardware abstraction layer; no end-user configuration remediation is available.

Fix this in Apq8053 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25696 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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