Transient denial of service via fence type confusion
Published Jun 3, 2024 · Updated Aug 1, 2024
Type confusion in Qualcomm Snapdragon Auto graphics firmware allows local users to cause a transient service interruption during DMA. When KGSL sets a fence callback to free a memory-entry object, an incorrect type conversion confuses the object type and permits the callback to act on the wrong object. Exploitation requires local access to the graphics path; the documented consequence is transient denial of service, with no confidentiality or integrity impact.
Summary
What happened
Type confusion in Qualcomm Snapdragon Auto graphics firmware allows local users to cause a transient service interruption during DMA. When KGSL sets a fence callback to free a memory-entry object, an incorrect type conversion confuses the object type and permits the callback to act on the wrong object. Exploitation requires local access to the graphics path; the documented consequence is transient denial of service, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2024-21478
- Published
- Jun 3, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- SA9000P Firmware
- Classifications
- CWE-476, CWE-704, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=*
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