Memory corruption via out-of-range camera-driver pointer
Published Jun 3, 2025 · Updated Jun 3, 2025
Memory corruption in Qualcomm Snapdragon camera drivers allows local users with low privileges to alter memory through a test-pattern IOCTL. The camera driver processes a test pattern generator IOCTL using an out-of-range pointer offset, causing memory corruption. Local low-privileged access is required, and Qualcomm has not disclosed the concrete post-corruption behavior.
Summary
What happened
Memory corruption in Qualcomm Snapdragon camera drivers allows local users with low privileges to alter memory through a test-pattern IOCTL. The camera driver processes a test pattern generator IOCTL using an out-of-range pointer offset, causing memory corruption. Local low-privileged access is required, and Qualcomm has not disclosed the concrete post-corruption behavior.
The record
- CVE
- CVE-2024-53017
- Published
- Jun 3, 2025
- Updated
- Jun 3, 2025
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-823
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 3, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 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=SDM429W
- Affected versionversion=Snapdragon 429 Mobile Platform
- Affected versionversion=WCN3620
- Affected versionversion=WCN3660B
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