Kernel crash and memory corruption via stale pointer
Published Sep 18, 2024 · Updated Aug 5, 2026
Memory corruption in the Linux kernel mwifiex driver allows nearby unauthenticated attackers to crash the kernel via wireless frames. mwifiex_get_priv_by_id returns an unused priv object without verifying bss_mode, leaving wiphy absent and stale histogram pointers reachable. Exposure requires a Marvell mwifiex device in AP or hotspot mode, or a removed virtual interface; crafted 802.11 traffic can cause a panic, disclose reused heap data, or corrupt freed heap memory.
Summary
What happened
Memory corruption in the Linux kernel mwifiex driver allows nearby unauthenticated attackers to crash the kernel via wireless frames. mwifiex_get_priv_by_id returns an unused priv object without verifying bss_mode, leaving wiphy absent and stale histogram pointers reachable. Exposure requires a Marvell mwifiex device in AP or hotspot mode, or a removed virtual interface; crafted 802.11 traffic can cause a panic, disclose reused heap data, or corrupt freed heap memory.
The record
- CVE
- CVE-2024-46755
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=3.2
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <1a05d8d02cfa3540ea5dbd6b39446bd3f515521f
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <9813770f25855b866b8ead8155b8806b2db70f6d
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <a12cf97cbefa139ef8d95081f2ea047cbbd74b7a
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <c145eea2f75ff7949392aebecf7ef0a81c1f6c14
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <c16916dd6c16fa7e13ca3923eb6b9f50d848ad03
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <c2618dcb26c7211342b54520b5b148c0d3471c8a
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <cb67b2e51b75f1a17bee7599c8161b96e1808a70
- Affected versionversion=93a1df48d224296fb527d32fbec4d5162828feb4 <d834433ff313838a259bb6607055ece87b895b66
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.
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