CVE-2022-22093

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

Published: 2022-09-16 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-22093 is rated Moderate Risk (41.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.10%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-22093

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.04% 0.10% +0.06%
2 2025-11-18 0.07% 0.04% -0.03%
3 2025-03-17 — 0.07% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-22093

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.9 [email protected]

Weakness enumeration for CVE-2022-22093

Affected software / configurations for CVE-2022-22093

Vendor Product Version Raw CPE
qualcomm aqt1000_firmware — cpe:2.3:o:qualcomm:aqt1000_firmware:-:*:*:*:*:*:*:*
qualcomm qca6390_firmware — cpe:2.3:o:qualcomm:qca6390_firmware:-:*:*:*:*:*:*:*
qualcomm qca6391_firmware — cpe:2.3:o:qualcomm:qca6391_firmware:-:*:*:*:*:*:*:*
qualcomm qca6420_firmware — cpe:2.3:o:qualcomm:qca6420_firmware:-:*:*:*:*:*:*:*
qualcomm qca6421_firmware — cpe:2.3:o:qualcomm:qca6421_firmware:-:*:*:*:*:*:*:*
qualcomm qca6426_firmware — cpe:2.3:o:qualcomm:qca6426_firmware:-:*:*:*:*:*:*:*
qualcomm qca6430_firmware — cpe:2.3:o:qualcomm:qca6430_firmware:-:*:*:*:*:*:*:*
qualcomm qca6431_firmware — cpe:2.3:o:qualcomm:qca6431_firmware:-:*:*:*:*:*:*:*
qualcomm qca6436_firmware — cpe:2.3:o:qualcomm:qca6436_firmware:-:*:*:*:*:*:*:*
qualcomm qcm6490_firmware — cpe:2.3:o:qualcomm:qcm6490_firmware:-:*:*:*:*:*:*:*
qualcomm qcs6490_firmware — cpe:2.3:o:qualcomm:qcs6490_firmware:-:*:*:*:*:*:*:*
qualcomm qrb5165_firmware — cpe:2.3:o:qualcomm:qrb5165_firmware:-:*:*:*:*:*:*:*
qualcomm qrb5165m_firmware — cpe:2.3:o:qualcomm:qrb5165m_firmware:-:*:*:*:*:*:*:*
qualcomm qrb5165n_firmware — cpe:2.3:o:qualcomm:qrb5165n_firmware:-:*:*:*:*:*:*:*
qualcomm qsm8350_firmware — cpe:2.3:o:qualcomm:qsm8350_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8_gen1_5g_firmware — cpe:2.3:o:qualcomm:sd_8_gen1_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8cx_firmware — cpe:2.3:o:qualcomm:sd_8cx_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8cx_gen2_firmware — cpe:2.3:o:qualcomm:sd_8cx_gen2_firmware:-:*:*:*:*:*:*:*
qualcomm sd765_firmware — cpe:2.3:o:qualcomm:sd765_firmware:-:*:*:*:*:*:*:*
qualcomm sd765g_firmware — cpe:2.3:o:qualcomm:sd765g_firmware:-:*:*:*:*:*:*:*
qualcomm sd768g_firmware — cpe:2.3:o:qualcomm:sd768g_firmware:-:*:*:*:*:*:*:*
qualcomm sd778g_firmware — cpe:2.3:o:qualcomm:sd778g_firmware:-:*:*:*:*:*:*:*
qualcomm sd780g_firmware — cpe:2.3:o:qualcomm:sd780g_firmware:-:*:*:*:*:*:*:*
qualcomm sd865_5g_firmware — cpe:2.3:o:qualcomm:sd865_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sd870_firmware — cpe:2.3:o:qualcomm:sd870_firmware:-:*:*:*:*:*:*:*
qualcomm sd888_firmware — cpe:2.3:o:qualcomm:sd888_firmware:-:*:*:*:*:*:*:*
qualcomm sd888_5g_firmware — cpe:2.3:o:qualcomm:sd888_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sdx55m_firmware — cpe:2.3:o:qualcomm:sdx55m_firmware:-:*:*:*:*:*:*:*
qualcomm sdxr2_5g_firmware — cpe:2.3:o:qualcomm:sdxr2_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sm7250p_firmware — cpe:2.3:o:qualcomm:sm7250p_firmware:-:*:*:*:*:*:*:*
qualcomm sm7315_firmware — cpe:2.3:o:qualcomm:sm7315_firmware:-:*:*:*:*:*:*:*
qualcomm sm7325p_firmware — cpe:2.3:o:qualcomm:sm7325p_firmware:-:*:*:*:*:*:*:*
qualcomm sm7450_firmware — cpe:2.3:o:qualcomm:sm7450_firmware:-:*:*:*:*:*:*:*
qualcomm sm8475_firmware — cpe:2.3:o:qualcomm:sm8475_firmware:-:*:*:*:*:*:*:*
qualcomm sm8475p_firmware — cpe:2.3:o:qualcomm:sm8475p_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9340_firmware — cpe:2.3:o:qualcomm:wcd9340_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9341_firmware — cpe:2.3:o:qualcomm:wcd9341_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9370_firmware — cpe:2.3:o:qualcomm:wcd9370_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9375_firmware — cpe:2.3:o:qualcomm:wcd9375_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9380_firmware — cpe:2.3:o:qualcomm:wcd9380_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9385_firmware — cpe:2.3:o:qualcomm:wcd9385_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3991_firmware — cpe:2.3:o:qualcomm:wcn3991_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3998_firmware — cpe:2.3:o:qualcomm:wcn3998_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6740_firmware — cpe:2.3:o:qualcomm:wcn6740_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6750_firmware — cpe:2.3:o:qualcomm:wcn6750_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6850_firmware — cpe:2.3:o:qualcomm:wcn6850_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6851_firmware — cpe:2.3:o:qualcomm:wcn6851_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6855_firmware — cpe:2.3:o:qualcomm:wcn6855_firmware:-:*:*:*:*:*:*:*
qualcomm wcn6856_firmware — cpe:2.3:o:qualcomm:wcn6856_firmware:-:*:*:*:*:*:*:*
qualcomm wcn7850_firmware — cpe:2.3:o:qualcomm:wcn7850_firmware:-:*:*:*:*:*:*:*
qualcomm wcn7851_firmware — cpe:2.3:o:qualcomm:wcn7851_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8810_firmware — cpe:2.3:o:qualcomm:wsa8810_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8815_firmware — cpe:2.3:o:qualcomm:wsa8815_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8830_firmware — cpe:2.3:o:qualcomm:wsa8830_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8832_firmware — cpe:2.3:o:qualcomm:wsa8832_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8835_firmware — cpe:2.3:o:qualcomm:wsa8835_firmware:-:*:*:*:*:*:*:*

References for CVE-2022-22093

cvelogic Threat Intelligence