CVE-2023-33107
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMemory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA memory corruption vulnerability exists in the Linux graphics driver subsystem. The flaw occurs in the IOCTL handler responsible for assigning shared virtual memory regions, where improper bounds checking or memory allocation handling during the IOCTL call leads to memory corruption. An attacker with local access could exploit this to elevate privileges or cause a denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Qualcomm firmware in useCheck system information or bootloader configuration for presence of any of these firmware names: Qualcomm 315 5G IoT Modem, Apq8017, Apq8064au, Aqt1000, Ar8031, Ar8035, C-V2X 9150, or Csra6620. This may appear in /proc/cpuinfo, dmesg, bootloader logs, or firmware version files.Affected if Any of the listed Qualcomm firmware components are present on the system
-
Verify graphics driver with SVM support is loadedCheck if a GPU driver supporting Shared Virtual Memory (SVM) is loaded. Look for modules like 'amdgpu' or similar graphics drivers in lsmod output, or check /dev/dri/* device nodes exist.Affected if A graphics driver with SVM capability is loaded and /dev/dri/* devices are present
-
Check SVM IOCTL interface accessibilityInspect permissions on graphics device nodes (typically /dev/dri/card* or /dev/dri/render*). Use 'ls -la /dev/dri/*' to view current access controls.Affected if The graphics device nodes are readable/writable by untrusted users or world-accessible
-
Confirm SVM feature is enabled in driverCheck driver configuration or module parameters for SVM/Shared Virtual Memory enablement. This may be visible in /sys/module/amdgpu/parameters/* or through driver-specific debug interfaces if SVM has been explicitly configured.Affected if SVM/Shared Virtual Memory feature is explicitly enabled in the graphics driver configuration
The system is affected if it runs any of the listed Qualcomm firmware versions AND has a graphics driver with SVM support enabled and accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided security patch for the Linux graphics driver. Update the kernel and associated graphics drivers to the patched version. For systems where immediate patching is not possible, consider restricting access to the graphics IOCTL interfaces or disabling untrusted GPU workloads.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-33107 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data