Local memory corruption via invalid IOCTL arguments
Published Aug 4, 2026 · Updated Aug 4, 2026
Memory corruption in Snapdragon Auto QAM8295P, QCA6696, and SA8295P allows local users to corrupt memory through malformed IOCTL requests. The affected device driver processes invalid IOCTL arguments and dereferences an untrusted pointer, causing memory corruption. Low-privilege local access is required; Qualcomm has not disclosed the driver or whether exploitation yields code execution rather than a crash or data corruption.
Summary
What happened
Memory corruption in Snapdragon Auto QAM8295P, QCA6696, and SA8295P allows local users to corrupt memory through malformed IOCTL requests. The affected device driver processes invalid IOCTL arguments and dereferences an untrusted pointer, causing memory corruption. Low-privilege local access is required; Qualcomm has not disclosed the driver or whether exploitation yields code execution rather than a crash or data corruption.
The record
- CVE
- CVE-2026-24083
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-822, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record 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=QAM8295P
- Affected versionversion=QCA6696
- Affected versionversion=SA8295P
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