Local memory corruption via concurrent IOCTL calls
Published Sep 2, 2024 · Updated Sep 5, 2024
Use-after-free in Qualcomm IPC firmware allows local users with low privileges to corrupt memory through concurrent IOCTL calls. The IPC device-control path processes simultaneous IOCTL requests without adequately protecting an object's lifetime, allowing one thread to access memory after another frees it. Low-privilege local access is required, and successful exploitation can alter protected data or interrupt the affected component.
Summary
What happened
Use-after-free in Qualcomm IPC firmware allows local users with low privileges to corrupt memory through concurrent IOCTL calls. The IPC device-control path processes simultaneous IOCTL requests without adequately protecting an object's lifetime, allowing one thread to access memory after another frees it. Low-privilege local access is required, and successful exploitation can alter protected data or interrupt the affected component.
The record
- CVE
- CVE-2024-38401
- Published
- Sep 2, 2024
- Updated
- Sep 5, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm WCN3660B Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 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