CVE-2024-33047
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 when the captureRead QDCM command is invoked from user-space.
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 QDCM (Qualcomm Display Color Manager) driver allowing a user-space application to trigger corruption via the captureRead command, potentially leading to privilege escalation or system compromise.
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 if your device uses an affected Qualcomm componentCheck system information or kernel config for presence of Qualcomm Fastconnect (6700/6900/7800), Qcm5430, Qcm6490, Qcs5430, Qcs6490, or Video Collaboration VC3 hardware. On Linux, check 'lspci' for wireless cards, or review boot logs for Qualcomm firmware identifiers.Affected if The system contains any of the listed Qualcomm components (Fastconnect 6700/6900/7800, Qcm5430, Qcm6490, Qcs5430, Qcs6490, or VC3 platform).
-
Verify the QDCM driver is loadedCheck for the QDCM driver module or service. On Linux, run 'lsmod | grep -i qdcm' or check '/sys/module/' for qdcm-related entries. Review dmesg for 'qdcm' or 'display color manager' initialization messages.Affected if The QDCM driver is present and loaded in the system.
-
Check if captureRead interface is exposed to user-spaceInspect QDCM driver permissions and device nodes. Look for character devices or sysfs entries related to QDCM captureRead functionality. Check file permissions on /dev/qdcm* or similar QDCM interfaces. Run 'ls -la /dev/*qdcm*' if such devices exist.Affected if The captureRead command pathway is accessible from user-space (device node has world-readable/writeable permissions or lacks restricted ACLs).
-
Review user-space access controls to QDCMCheck SELinux/AppArmor policies or device file ownership. Determine if any user-space application can access QDCM interfaces without privilege escalation. Examine system policies for qdcm-related access rules.Affected if User-space applications without elevated privileges can invoke the captureRead command against the QDCM driver.
A system is affected if it contains any of the listed Qualcomm components (which all versions are) with the QDCM driver loaded and the captureRead interface exposed to unprivileged user-space access.
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 vendor security patches to the QDCM driver; until then, restrict user-space access to QDCM interfaces or disable the captureRead command pathway.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33047 — 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-2024-33047 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