Kernel heap corruption via unchecked WMM length
Published May 5, 2020 · Updated Aug 4, 2024
Heap-based buffer overflow in the Linux kernel before 5.5.4 allows physically proximate attackers to corrupt kernel memory via a malicious Wi-Fi AP. mwifiex_ret_wmm_get_status() copies an AP-supplied WMM element into a fixed-size destination using vend_hdr.len + 2 without first checking the destination size. The target must use the Marvell mwifiex driver and interact with an attacker-controlled access point; the immediate consequence is kernel heap corruption.
Summary
What happened
Heap-based buffer overflow in the Linux kernel before 5.5.4 allows physically proximate attackers to corrupt kernel memory via a malicious Wi-Fi AP. mwifiex_ret_wmm_get_status() copies an AP-supplied WMM element into a fixed-size destination using vend_hdr.len + 2 without first checking the destination size. The target must use the Marvell mwifiex driver and interact with an attacker-controlled access point; the immediate consequence is kernel heap corruption.
The record
- CVE
- CVE-2020-12654
- Published
- May 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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