Memory corruption via double-freed WMI command buffer
Published Nov 4, 2024 · Updated Nov 16, 2024
Stack-based buffer overflow in Qualcomm Snapdragon firmware allows local users to corrupt memory through an IOCTL in an invalid device state. The host-side path processes the IOCTL while the device is invalid and can free the WMI command buffer twice, corrupting memory. Low-privileged local access is required; Qualcomm has not disclosed the affected IOCTL, code path, or a more specific consequence than memory corruption.
Summary
What happened
Stack-based buffer overflow in Qualcomm Snapdragon firmware allows local users to corrupt memory through an IOCTL in an invalid device state. The host-side path processes the IOCTL while the device is invalid and can free the WMI command buffer twice, corrupting memory. Low-privileged local access is required; Qualcomm has not disclosed the affected IOCTL, code path, or a more specific consequence than memory corruption.
The record
- CVE
- CVE-2024-38410
- Published
- Nov 4, 2024
- Updated
- Nov 16, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm WCN3660B Firmware
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 16, 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