Memory corruption via concurrent HAB channel teardown
Published Oct 7, 2024 · Updated Oct 7, 2024
Use-after-free corruption in Qualcomm Snapdragon HAB firmware allows local users with high privileges to corrupt memory through IOCTL calls. The HAB virtual-channel IOCTL path permits one process to destroy a channel while another process creates it, leaving the channel lifetime unsynchronized. The race requires high local privileges; Qualcomm reports memory corruption but does not disclose the specific post-corruption behavior.
Summary
What happened
Use-after-free corruption in Qualcomm Snapdragon HAB firmware allows local users with high privileges to corrupt memory through IOCTL calls. The HAB virtual-channel IOCTL path permits one process to destroy a channel while another process creates it, leaving the channel lifetime unsynchronized. The race requires high local privileges; Qualcomm reports memory corruption but does not disclose the specific post-corruption behavior.
The record
- CVE
- CVE-2024-23370
- Published
- Oct 7, 2024
- Updated
- Oct 7, 2024
- Vendor
- Qualcomm
- Product
- QCA6698AQ Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 7, 2024CVE publishedPublication date reported by the CVE source.
- Oct 7, 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