Memory corruption via use-after-free during IOCTL handling
Published Mar 4, 2024 · Updated Aug 8, 2024
Use-after-free in Qualcomm Automotive Multimedia firmware allows local users to corrupt memory by invoking crafted IOCTL calls. The Automotive Multimedia IOCTL path accesses an object after its memory has been freed, but Qualcomm has not disclosed the function or object. Local execution on a device containing an affected chipset is required, and exploitation can compromise confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Qualcomm Automotive Multimedia firmware allows local users to corrupt memory by invoking crafted IOCTL calls. The Automotive Multimedia IOCTL path accesses an object after its memory has been freed, but Qualcomm has not disclosed the function or object. Local execution on a device containing an affected chipset is required, and exploitation can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-43547
- Published
- Mar 4, 2024
- Updated
- Aug 8, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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