dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-22093

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 or temporary denial of service due to improper handling of concurrent hypervisor operations to attach or detach IRQs from virtual interrupt sources in Snapdragon Compute, Snapdragon Connectivity, 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 confidence

This is a hypervisor vulnerability in Qualcomm Snapdragon chips where improper synchronization during concurrent IRQ attach/detach operations on virtual interrupt sources leads to memory corruption or temporary denial of service. The race condition occurs when multiple threads attempt to modify IRQ-to-virtual-source mappings simultaneously without proper locking, causing memory safety violations.

MitigationApply vendor firmware updates (OEM patches) for affected Snapdragon devices; until patches are available, minimize exposure by restricting untrusted VM access to IRQ assignment operations and monitoring for exploitation indicators.

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
Aqt1000 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6420 FirmwareOperating system
Affected:all versions
Qca6421 FirmwareOperating system
Affected:all versions
Qca6426 FirmwareOperating system
Affected:all versions
Qca6430 FirmwareOperating system
Affected:all versions
Qca6431 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 firmware version
    Check the system firmware/bootloader or use 'cat /proc/cmdline' or 'dmesg' to look for firmware version strings like Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, or Qca6431
    Affected if The firmware version matches any of the listed affected products (all versions of Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, Qca6431)
  2. Confirm hypervisor is in use
    Check if a hypervisor is active by running 'dmesg | grep -i hypervisor' or 'systemd-detect-virt'
    Affected if A hypervisor is running on Qualcomm Snapdragon hardware with the affected firmware
  3. Verify IRQ virtualization is enabled
    Check hypervisor configuration for IRQ routing settings, typically found in hypervisor config files or via 'xl info' (Xen) or 'virsh dumpxml' (KVM) for IRQ assignments
    Affected if IRQ-to-virtual-source mapping configuration is present and modifiable by the hypervisor
  4. Check for untrusted VM IRQ access
    Review hypervisor policies for PCI passthrough or IRQ assignment permissions granted to VMs, particularly untrusted or tenant VMs
    Affected if Untrusted VMs have permission to perform IRQ attach/detach operations on virtual interrupt sources
  5. Look for exploitation indicators
    Review system logs (dmesg, hypervisor logs) for signs of memory corruption, kernel panics, or unexpected VM crashes related to IRQ handling
    Affected if Logs show memory corruption, unexpected reboots, or denial of service events coinciding with concurrent IRQ operations

The environment is affected if it runs any version of the listed Qualcomm firmware with an active hypervisor that exposes IRQ virtualization to VMs, particularly untrusted ones.

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 firmware updates (OEM patches) for affected Snapdragon devices; until patches are available, minimize exposure by restricting untrusted VM access to IRQ assignment operations and monitoring for exploitation indicators.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,920
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22093 — 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-22093 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