Memory corruption via unvalidated channel ID
Published May 6, 2024 · Updated Dec 16, 2025
Memory corruption in Qualcomm Snapdragon secure processor firmware allows local users to corrupt memory through a crafted channel ID. The secure processor accepts a user-supplied channel ID without validating it before using it, causing memory corruption. Local low-privilege access is required; Qualcomm does not disclose whether the corruption causes a crash, code execution, or another concrete effect.
Summary
What happened
Memory corruption in Qualcomm Snapdragon secure processor firmware allows local users to corrupt memory through a crafted channel ID. The secure processor accepts a user-supplied channel ID without validating it before using it, causing memory corruption. Local low-privilege access is required; Qualcomm does not disclose whether the corruption causes a crash, code execution, or another concrete effect.
The record
- CVE
- CVE-2024-21476
- Published
- May 6, 2024
- Updated
- Dec 16, 2025
- Vendor
- Qualcomm
- Product
- Qualcomm QCA6431 Firmware
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo