basicsecurity.net
Proof, not just disclosure.
Threats / Qualcomm / CVE-2023-33107
CVE-2023-33107 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Qualcomm Multiple Chipsets vulnerability

Multiple Qualcomm chipsets contain an integer overflow vulnerability in Graphics Linux during shared virtual memory region assignment via IOCTL calls, enabling memory corruption.

Verdict

Today item — known-exploited.

Integer overflow in memory handling allows local attackers to corrupt kernel memory and potentially escalate privileges or cause denial of service on affected Qualcomm chipset-based devices.

CISA KEV Yes · 2023-12-053EPSS 0.00892 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00892 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-190 Integer Overflow — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-190 · Integer OverflowMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
Gain local code execution access to a device running affected Qualcomm chipsets.
Business
Device compromise enables unauthorized access to sensitive data and system functions.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Trigger integer overflow during IOCTL shared virtual memory assignment to corrupt kernel memory structures.
Business
Memory corruption destabilizes system integrity and creates exploitation pathways for privilege escalation.
3

Lateral reach — past segmentation narrative 3

Attacker
Escalate privileges from user-level to kernel-level access through corrupted memory state.
Business
Full system compromise allows attacker to bypass security controls and maintain persistent access.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 5 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by qualcomm (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by qualcommCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.