Exploited CVEs / Qualcomm / CVE-2022-22071

CVE-2022-22071

Qualcomm Multiple Chipsets Use-After-Free Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2023-12-26 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV
7.8
CVSS base
<1%
EPSS exploit probability
High
Severity
2023-12-05
Added to KEV
2023-12-26 (past due)
CISA due date

Actively exploited Qualcomm Multiple Chipsets vulnerability, High severity, CVSS 7.8. Added to the CISA KEV catalog 2023-12-05.

Senserva AI read on CVE-2022-22071CISA required actionOfficial fix for CVE-2022-22071Admin questions

Senserva AI Opinion for CVE-2022-22071

A use-after-free across multiple Qualcomm chipsets, triggered when process shell memory is freed via an IOCTL munmap call during process initialization. Its December 2023 KEV listing with a 0 percent EPSS score points to narrow, targeted use rather than mass exploitation, which is typical for mobile chipset bugs. Exposure depends on device vendors shipping Qualcomm's fix, so older unsupported Android hardware stays vulnerable forever.

Do this: Check that managed Android devices are on current security patch levels and retire handsets no longer receiving vendor updates.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2022-22071

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2023-12-26; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2022-22071

Published
2023-12-05
Last revised
2023-12-05
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
  • 2023-12-05 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 7.8; EPSS first scored at 0.4%
  • 2026-08-08 EPSS 0.4% to 0.5%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2023-12-26 (past due).

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Official fix for CVE-2022-22071

Check the vendor's security advisory channel for the patched Multiple Chipsets versions and workarounds.

CISA KEV entry

Common questions about CVE-2022-22071

Is CVE-2022-22071 actively exploited?

Yes. CVE-2022-22071 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2023-12-05, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.

What is the CISA deadline and required action for CVE-2022-22071?

CISA set the federal (BOD 22-01) remediation due date at 2023-12-26, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

What fixes CVE-2022-22071?

Check the vendor's security advisory for the patched Multiple Chipsets versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2022-22071?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2022-22071's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Qualcomm CVEs
CVE-2026-21385CVE-2025-27038CVE-2025-21479CVE-2025-21480CVE-2024-43047CVE-2023-33107CVE-2023-33106CVE-2023-33063

All Qualcomm exploited CVEs on one page: Qualcomm vulnerabilities actively exploited.

Authoritative references
CVE recordNVD detailCISA KEV catalogFIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.