Local crash or kernel leak via SCO getsockopt
Published Feb 19, 2021 · Updated Aug 4, 2024
NULL pointer dereference in Linux Kernel before 5.11 allows local users to crash the system or leak kernel information via SCO socket options. The sco_sock_getsockopt function in net/bluetooth/sco.c dereferences a missing socket connection when handling BT_SNDMTU or BT_RCVMTU, causing a kernel NULL pointer fault. Exploitation requires local access with the relevant Bluetooth socket capability; the consequence is system denial of service or disclosure of kernel memory information.
Summary
What happened
NULL pointer dereference in Linux Kernel before 5.11 allows local users to crash the system or leak kernel information via SCO socket options. The sco_sock_getsockopt function in net/bluetooth/sco.c dereferences a missing socket connection when handling BT_SNDMTU or BT_RCVMTU, causing a kernel NULL pointer fault. Exploitation requires local access with the relevant Bluetooth socket capability; the consequence is system denial of service or disclosure of kernel memory information.
The record
- CVE
- CVE-2020-35499
- Published
- Feb 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel 5.11
What conditions does exploitation require?
What is affected?
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