CVE-2023-33106
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 while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.
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 confidenceMemory corruption vulnerability in the KGSL (Kernel Graphics Support Layer) GPU driver's IOCTL_KGSL_GPU_AUX_COMMAND handler when processing an excessively large list of sync points, potentially allowing local privilege escalation or 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 KGSL driver presenceCheck if the KGSL (Kernel Graphics Support Layer) driver is loaded on the system by examining kernel modules: lsmod | grep kgsl or check /sys/module/ for kgsl presenceAffected if The KGSL driver module is loaded and the system uses Qualcomm GPU hardware
-
Determine Qualcomm firmware componentsExamine system firmware or bootloader output for presence of Qualcomm chipsets (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6800/6900/7800). Check /lib/firmware/qcom/ or device tree bindings for these componentsAffected if Any of the listed Qualcomm firmware components (Ar8035, Csra6620, Csra6640, Fastconnect series) are present in the system
-
Verify ioctl interface accessibilityCheck if the IOCTL_KGSL_GPU_AUX_COMMAND interface is exposed by examining /dev/kgsl-3d0 or similar device nodes and verifying read/write permissionsAffected if The KGSL device node exists and is accessible, enabling the vulnerable ioctl path
-
Check kernel version and driver versionQuery the KGSL driver version via cat /sys/class/kgsl/kgsl-3d0/gpu_version or similar sysfs interface, and compare against any available patch informationAffected if The KGSL driver version is present and matches hardware known to contain this vulnerability
A system is affected if it contains any of the listed Qualcomm firmware components (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6800/6900/7800) with the KGSL driver loaded and the ioctl interface accessible, since all versions of these products are vulnerable.
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 kernel security updates from the device/OS vendor that patch the KGSL driver memory handling in IOCTL_KGSL_GPU_AUX_COMMAND; prioritize updates for devices with graphics/GPU functionality.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33106 — 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-33106 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