CVE-2024-33065
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 taking snapshot when an offset variable is set by camera driver.
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 · low confidenceA memory corruption vulnerability exists in the camera subsystem that triggers during snapshot operations. The vulnerability is activated when an offset variable is set by the camera driver, leading to potential arbitrary code execution 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 the Snapdragon SoC modelCheck the device or system information to determine the specific Snapdragon processor model. On Linux, this can be done with 'cat /proc/cpuinfo' or checking 'lspci' output, or by checking the device/board specifications.Affected if The SoC model is one of: sc8180x (Ac/Af variants), sc8180xp (Ac/Aa/Ab/Af variants), or sc8280xp (Ab/Bb variants)
-
Verify camera subsystem is activeCheck if the camera driver is loaded and the camera subsystem is accessible. On Linux, use 'lsmod | grep camera' or check /dev/video* devices exist.Affected if Camera subsystem modules are loaded and camera devices are present in the system
-
Check firmware version if accessibleIf the camera firmware version is exposed through system interfaces (such as via 'v4l2-ctl --all', camera API diagnostics, or firmware logs), retrieve and document it.Affected if The firmware version cannot be determined or is not publicly documented as patched (note: all versions are affected according to the advisory)
-
Confirm device uses affected compute platformReview the device documentation, BIOS/UEFI information, or system specifications to confirm the exact platform variant (such as sc8180xp Ab or sc8280xp Bb).Affected if The device implements one of the listed affected Snapdragon compute platform variants
A user is affected if their device incorporates any of the listed Snapdragon 8cx Gen 2/3 or 8cx Compute Platform variants (sc8180x, sc8180xp, or sc8280xp) and has the camera subsystem enabled, since all firmware versions of these platforms 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 vendor-provided patches or firmware updates for the camera driver. Until an update is available, restrict camera access to trusted applications and monitor for unusual device behavior.
- Consultation3.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33065 — 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-33065 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