CVE-2023-33107VulnerabilityPublished 5 Dec 2023Updated 21 Oct 2025

CVE-2023-33107: Qualcomm Snapdragon · Integer Overflow or Wraparound

Affects Qualcomm SnapdragonSource CVE Database V5

Exploited in the wild · KEV due 26 Dec 2023 : apply the vendor's fix or mitigations to Qualcomm Snapdragon now.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.4High

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 26 Dec 2023 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 5 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV the same day as disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Qualcomm, Inc.
17 May 202309:28 UTC, 202 days before disclosure
CVE published
on cve.org
5 Dec 202303:04 UTC, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
5 Dec 2023, the same day as disclosure
KEV remediation due
US federal deadline
26 Dec 2023, 21 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Description

CVE-2023-33107 is a high-severity integer overflow vulnerability in Qualcomm Snapdragon platforms affecting a wide range of mobile, IoT, automotive, and wearable devices. The flaw occurs in the Graphics Linux driver during IOCTL calls when assigning shared virtual memory regions, leading to memory corruption. Exploitation requires local access and no user interaction or privileges, potentially allowing attackers to execute arbitrary code or cause denial of service. Although no known exploits are reported, the broad product impact and high CVSS score indicate significant risk. European organizations using devices with affected Snapdragon chipsets, especially in telecommunications, automotive, and IoT sectors, face confidentiality, integrity, and availability threats. Mitigation involves applying vendor patches once available, restricting local access, and monitoring for anomalous behavior. Countries with high smartphone penetration and automotive industries, such as Germany, France, and the UK, are most likely impacted. The vulnerability's ease of exploitation without privileges and its broad scope warrant a high severity rating. Defenders should prioritize patch management and device security controls to mitigate potential exploitation.

Impact

For European organizations, the impact of CVE-2023-33107 is significant due to the widespread use of Qualcomm Snapdragon chipsets in smartphones, IoT devices, automotive systems, and industrial equipment. Confidentiality risks include potential data leakage from compromised devices, while integrity risks involve unauthorized code execution or manipulation of device operations. Availability could be affected by denial-of-service conditions triggered by memory corruption. Telecommunications providers and enterprises relying on mobile and IoT infrastructure may experience service disruptions or breaches. Automotive manufacturers and suppliers using affected Snapdragon automotive platforms could face safety and operational risks. The vulnerability's local access requirement limits remote exploitation but does not eliminate risk in environments where devices are accessible to insiders or compromised applications. Given the critical role of mobile and embedded devices in European digital infrastructure, exploitation could undermine trust and operational continuity. The lack of current public exploits provides a window for mitigation, but the high severity and broad impact necessitate proactive defense measures.

Mitigation

1. Apply official Qualcomm patches immediately once released for all affected Snapdragon platforms and devices. 2. Restrict local access to devices by enforcing strict user permissions and application sandboxing to prevent untrusted code from invoking vulnerable IOCTL calls. 3. Employ endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts, such as unusual IOCTL activity or memory corruption symptoms. 4. For organizations deploying IoT or automotive devices, implement network segmentation and device hardening to limit exposure to potentially malicious local actors. 5. Coordinate with device manufacturers and service providers to ensure firmware and software updates are deployed promptly. 6. Conduct regular security audits and penetration testing focusing on local privilege escalation vectors. 7. Educate users and administrators about the risks of installing untrusted applications that could exploit local vulnerabilities. 8. Maintain an inventory of devices with affected Snapdragon chipsets to prioritize patching and monitoring efforts. 9. Consider deploying runtime application self-protection (RASP) or similar technologies on critical devices to detect and block exploitation attempts in real time.

Summary

CVE-2023-33107 is an integer overflow vulnerability classified under CWE-190 found in the Graphics Linux driver component of Qualcomm Snapdragon platforms. The vulnerability arises during the assignment of shared virtual memory regions via IOCTL system calls, where improper handling of integer values leads to overflow or wraparound conditions. This results in memory corruption, which can be exploited to achieve arbitrary code execution, privilege escalation, or denial of service on affected devices. The vulnerability affects a vast array of Qualcomm Snapdragon products, including mobile platforms (e.g., Snapdragon 8 Gen 1, Snapdragon 888), IoT modems, automotive platforms, wearable devices, and connectivity modules. The flaw requires local attacker access but no privileges or user interaction, making it easier for malicious local applications or compromised processes to exploit. The CVSS v3.1 score is 8.4 (high), reflecting the vulnerability's potential to impact confidentiality, integrity, and availability severely. No public exploits are currently known, but the extensive list of affected platforms and the critical nature of the flaw necessitate urgent attention. The flaw's exploitation could compromise device security, leading to unauthorized access or disruption of services on devices widely used in consumer electronics, industrial IoT, automotive systems, and telecommunications infrastructure.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 28 Oct 2025, 23:49 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats