Kernel crash via oversized socket address write
Published Mar 24, 2020 · Updated Aug 4, 2024
Stack buffer overflow in the Linux kernel before 5.5.8 allows local users to crash the system through /dev/vhost-net ioctl calls. get_raw_socket calls the socket getname operation into a fixed-size sockaddr buffer before confirming AF_PACKET, so an AX.25 address overwrites the kernel stack. Access to /dev/vhost-net and the ability to supply a crafted socket descriptor are required; successful exploitation interrupts the host by crashing it.
Summary
What happened
Stack buffer overflow in the Linux kernel before 5.5.8 allows local users to crash the system through /dev/vhost-net ioctl calls. get_raw_socket calls the socket getname operation into a fixed-size sockaddr buffer before confirming AF_PACKET, so an AX.25 address overwrites the kernel stack. Access to /dev/vhost-net and the ability to supply a crafted socket descriptor are required; successful exploitation interrupts the host by crashing it.
The record
- CVE
- CVE-2020-10942
- Published
- Mar 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 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
- syzbot kernel-crash reproducerproof of concept · demonstrated
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