Local memory corruption via interrupted IOCTL use-after-free
Published May 6, 2024 · Updated Aug 1, 2024
Use-after-free in Qualcomm Graphics Linux allows local users to corrupt memory by interrupting an IOCTL call with a signal. The interrupted IOCTL can retain a reference after its backing object is freed, although Qualcomm has not identified the affected function or object. A local process can trigger corruption without prior privileges or user interaction; the public record does not specify whether the result is code execution, a crash, or another failure mode.
Summary
What happened
Use-after-free in Qualcomm Graphics Linux allows local users to corrupt memory by interrupting an IOCTL call with a signal. The interrupted IOCTL can retain a reference after its backing object is freed, although Qualcomm has not identified the affected function or object. A local process can trigger corruption without prior privileges or user interaction; the public record does not specify whether the result is code execution, a crash, or another failure mode.
The record
- CVE
- CVE-2024-23354
- Published
- May 6, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 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