Local memory corruption via private-command IOCTL
Published Dec 2, 2024 · Updated Dec 3, 2024
Memory corruption in Qualcomm WLAN drivers allows local users to corrupt kernel memory through a generic private-command IOCTL. The user-space IOCTL handler processes the command without sufficient buffer-bound restrictions, but Qualcomm has not disclosed the affected function or buffer. Exploitation requires low-privileged local access and can compromise data or interrupt the device within the driver context.
Summary
What happened
Memory corruption in Qualcomm WLAN drivers allows local users to corrupt kernel memory through a generic private-command IOCTL. The user-space IOCTL handler processes the command without sufficient buffer-bound restrictions, but Qualcomm has not disclosed the affected function or buffer. Exploitation requires low-privileged local access and can compromise data or interrupt the device within the driver context.
The record
- CVE
- CVE-2024-43049
- Published
- Dec 2, 2024
- Updated
- Dec 3, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm WCN3660B Firmware
- Classifications
- CWE-119, CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 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