CVE-2023-33107
Memory Safety in Qualcomm 315 5G Iot Modem Firmware
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-33107 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Qualcomm 315 5G Iot Modem Firmware. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 44% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-33107 is a memory corruption vulnerability, tracked under CWE-190, that occurs in the Graphics Linux component when assigning a shared virtual memory region during an IOCTL call. The flaw affects Qualcomm platforms that incorporate this Linux graphics driver code and carries a CVSS 3.1 base score of 8.4, reflecting high impact on confidentiality, integrity, and availability.
An attacker with local access and no privileges can invoke the affected IOCTL to trigger the corruption, enabling arbitrary code execution or denial of service within the graphics subsystem. Because the attack vector is local and requires no user interaction or elevated permissions, the issue can be reached from an untrusted application or compromised process running on the device.
Qualcomm’s December 2023 security bulletin addresses the issue with patches for impacted chipsets and software releases. The vulnerability also appears in CISA’s catalog of known exploited vulnerabilities, confirming observed in-the-wild use; the current EPSS score of 0.004 remains low and shows no material upward trajectory.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-37296
Vulnerability Data
Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
- CWE(s)
- KEV Date Added
- 05 December 2023
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.