CVERadar
HIGH · CVSS 3.1 7.8CISA KEV · added 2023-12-05Public PoCEPSS 1.02% (p64)Threat level 54

CVE-2023-33107: Qualcomm Multiple Chipsets Integer Overflow Vulnerability

Qualcomm · Multiple Chipsets · NVD published 2023-12-05 · posted 2023-12-05 · last modified 2026-06-17

CVE-2023-33107 at a glance

CVE-2023-33107 is a high-severity Integer Overflow vulnerability in Qualcomm Multiple Chipsets, with a CVSS 3.1 base score of 7.8. NVD published it on 2023-12-05 and classifies the weakness as CWE-190. CISA added it to the Known Exploited Vulnerabilities catalog on 2023-12-05; the federal remediation due date is 2023-12-26. Public exploit code: 3 public GitHub proof-of-concept repositories from 3 accounts, with the earliest exploit evidence dated 2023-12-05. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 1.02% (percentile 63.7, scored 2026-11-09). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Execution, inferred from the CWE and the description. Its CVERadar threat level is 54/100.

What it is

Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

WeaknessCWE-190 definition
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: NIST NVD)
CISA due date2023-12-26 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsExecution

What this means for a small business

CISA added CVE-2023-33107 to its Known Exploited Vulnerabilities catalog on 2023-12-05. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs Qualcomm Multiple Chipsets, put this at the top of the patch list. CISA gave US federal agencies until 2023-12-26 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Install the latest update from Qualcomm. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
  • If you cannot patch yet. Follow CISA's required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
  • Check your exposure. List every device that runs Qualcomm Multiple Chipsets, including laptops that rarely come into the office, and check which version each one has installed.
  • When to call IT support. Call your IT support provider now if you run Qualcomm Multiple Chipsets and cannot confirm it is updated, if some devices running it went unpatched for weeks, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

Patching closes the hole, but someone still has to watch the endpoints; managed endpoint protection from LayerLogix covers EDR and MDR.

Built from the CISA KEV entry and the NVD record for CVE-2023-33107; nothing here goes beyond those sources.

Exploitation evidence

First exploit evidence seen: 2023-12-05 (earliest date across the sources below).

Exploited in the wild

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2026-02-05. Most starred: 264312431/picohaxx (9 stars), view the 264312431/picohaxx repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2023-33107 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 54/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1203 Exploitation for Client Execution Inferred

Inferred from CWE CWE-190

Patches, mitigations and detection

CISA required action

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. (source: CISA KEV)

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
  • M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
  • M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.

Detection Generic guidance

  • Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources