Kernel memory corruption via DMA fence use-after-free
Published Aug 5, 2024 · Updated Aug 15, 2024
Use-after-free in Qualcomm graphics kernel firmware allows local users to corrupt kernel memory through a request that creates a DMA fence. The public fix changes kgsl_add_fence_event in kgsl_sync.c, but Qualcomm has not disclosed which object is freed before the function reuses it. Exploitation requires local access to an affected device and no prior privileges or user interaction; the corruption occurs in kernel context.
Summary
What happened
Use-after-free in Qualcomm graphics kernel firmware allows local users to corrupt kernel memory through a request that creates a DMA fence. The public fix changes kgsl_add_fence_event in kgsl_sync.c, but Qualcomm has not disclosed which object is freed before the function reuses it. Exploitation requires local access to an affected device and no prior privileges or user interaction; the corruption occurs in kernel context.
The record
- CVE
- CVE-2024-23382
- Published
- Aug 5, 2024
- Updated
- Aug 15, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.
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