Threats / Qualcomm / CVE-2022-22071
CVE-2022-22071
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Qualcomm Multiple Chipsets vulnerability
Multiple Qualcomm chipsets contain a use-after-free vulnerability in process shell memory handling during initialization, triggered via IOCTL munmap calls.
Verdict
Today item — known-exploited.
A use-after-free flaw in Qualcomm chipset memory management allows local attackers to corrupt memory state during process initialization, potentially enabling privilege escalation or denial of service on affected devices.
CISA KEV Yes · 2023-12-055EPSS 0.0045 (verify live)6CVSS 8.43CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-12-05).
Probability (EPSS)
EPSS 0.0045 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.4 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 539 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious IOCTL munmap sequence timed to coincide with process initialization to trigger use-after-free conditions.
Business
Device stability and security posture are compromised by memory corruption exploitable for privilege escalation.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the freed memory reference to read or write sensitive kernel data structures.
Business
Confidentiality and integrity of system operations are at risk, potentially exposing user data or enabling further attacks.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges by corrupting process control structures accessible through the use-after-free window.
Business
Complete device compromise becomes possible, undermining trust in the platform and exposing customer data.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05