CVE-2024-53033
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 doing Escape call when user provides valid kernel address in the place of valid user buffer address.
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 confidenceThis is a kernel-level vulnerability where improper validation allows a user to pass a kernel-space address instead of a user-space buffer address to an Escape system call. This confuses the kernel's memory management leading to memory corruption, 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 firmware componentsCheck system firmware, driver, or hardware information for presence of Fastconnect 6900/7800, Sc8380xp, Wcd9380/9385, or Wsa8840/8845/8845h components. On Linux, this may appear in dmesg, /sys/devices, or firmware blobs. On Android, check /vendor/firmware or via 'getprop' for radio firmware versions.Affected if Any of the affected Qualcomm components (Fastconnect 6900, Fastconnect 7800, Sc8380xp, Wcd9380, Wcd9385, Wsa8840, Wsa8845, Wsa8845h) are present on the system
-
Verify Escape system call availabilityCheck if the Escape system call interface is exposed. This may be visible in system call tables, kernel configs (CONFIG_ESCAPE or similar), or through debugging interfaces. Look for Escape-related entries in /proc/kallsyms or kernel symbol files if accessible.Affected if The Escape system call handler is compiled into the kernel or available through the firmware interface
-
Check user-space access to Escape callDetermine whether user-space applications can invoke the Escape system call. Review any available documentation, system call number assignments, or test access through existing exploit code or proof-of-concept that attempts the syscall.Affected if User-space processes can trigger the Escape system call with arbitrary parameters
-
Confirm kernel address handling in Escape pathInspect memory management behavior when Escape calls receive pointers. This requires kernel debugging capabilities or review of any available kernel source code for the Escape call handler to verify lack of address space boundary validation.Affected if The Escape call handler does not validate that passed pointers are within user address space before use
If the system contains any of the affected Qualcomm firmware components (Fastconnect 6900/7800, Sc8380xp, Wcd9380/9385, Wsa8840/8845/8845h) and the Escape system call is accessible from user-space, the environment is affected by CVE-2024-53033.
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 dataImplement strict address space validation in the Escape call handler to verify the provided address lies within user address space before use, rejecting kernel-space pointers.
- Consultation6.0 h
- Implementation8.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 $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53033 — 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-53033 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