Threats / Qualcomm / CVE-2023-33063
CVE-2023-33063
· 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 DSP Services triggered by remote calls from HLOS to DSP, enabling memory corruption.
Verdict
Today item — known-exploited.
A use-after-free flaw in Qualcomm chipset DSP Services allows remote exploitation through HLOS-to-DSP communication channels. Active exploitation in the wild indicates practical attack feasibility despite low EPSS score.
CISA KEV Yes · 2023-12-055EPSS 0.007 (verify live)6CVSS 7.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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.007 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/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 — CNA-assigned (CVE.org); 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 the same day 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 remote call from HLOS to DSP that triggers reuse of freed memory in the DSP Services handler.
Business
Device firmware integrity is compromised, enabling persistent compromise of baseband and application processors.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the memory corruption to execute arbitrary code within DSP context with elevated privileges.
Business
Attackers gain control over cellular modem and sensor processing, bypassing OS-level security boundaries.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage DSP code execution to intercept communications, exfiltrate encryption keys, or modify network traffic.
Business
Confidentiality and integrity of user communications are lost; regulatory compliance obligations are violated.
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