Kernel memory corruption via unchecked receive fragments
Published Apr 29, 2020 · Updated Aug 4, 2024
Array overflow in the Linux kernel mt76 driver before 5.5.10 allows local users with administrative privileges to corrupt kernel memory. The mt76_add_fragment function passed nr_frags directly as the skb_shared_info frags index without checking the fixed array bound before adding a receive fragment. Administrative privileges and affected MediaTek mt76 wireless hardware are required; corruption can crash the kernel or disclose kernel information.
Summary
What happened
Array overflow in the Linux kernel mt76 driver before 5.5.10 allows local users with administrative privileges to corrupt kernel memory. The mt76_add_fragment function passed nr_frags directly as the skb_shared_info frags index without checking the fixed array bound before adding a receive fragment. Administrative privileges and affected MediaTek mt76 wireless hardware are required; corruption can crash the kernel or disclose kernel information.
The record
- CVE
- CVE-2020-12465
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 29, 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.
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