Kernel memory corruption via shared-memory race
Published Nov 4, 2024 · Updated Nov 8, 2024
Memory corruption in Camera_Linux on affected Qualcomm Snapdragon platforms allows local users with high privileges to corrupt kernel memory. Camera_Linux accesses shared memory without preventing a user application from modifying that memory asynchronously during kernel access. Exploitation requires privileged local application access and successful timing of the race, with confidentiality, integrity, and availability consequences.
Summary
What happened
Memory corruption in Camera_Linux on affected Qualcomm Snapdragon platforms allows local users with high privileges to corrupt kernel memory. Camera_Linux accesses shared memory without preventing a user application from modifying that memory asynchronously during kernel access. Exploitation requires privileged local application access and successful timing of the race, with confidentiality, integrity, and availability consequences.
The record
- CVE
- CVE-2024-33032
- Published
- Nov 4, 2024
- Updated
- Nov 8, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 8, 2024Record 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=0 <=*
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