Bluetooth management access via socket-opener authorization bypass
Published May 26, 2023 · Updated Aug 2, 2024
Incorrect authorization in Linux Kernel before 6.4-rc1 allows local users to issue privileged Bluetooth management commands via HCI sockets. In net/bluetooth/hci_sock.c, hci_sock_ioctl checks the ioctl caller's CAP_NET_ADMIN status rather than the HCI socket opener's status, then sets HCI_SOCK_TRUSTED on a socket opened without that capability. A local account can pass the socket to a setuid or CAP_NET_ADMIN program that invokes ioctl on an inherited descriptor, then pair unwanted devices, block pairing, read out-of-band data, or interrupt Bluetooth communication.
Summary
What happened
Incorrect authorization in Linux Kernel before 6.4-rc1 allows local users to issue privileged Bluetooth management commands via HCI sockets. In net/bluetooth/hci_sock.c, hci_sock_ioctl checks the ioctl caller's CAP_NET_ADMIN status rather than the HCI socket opener's status, then sets HCI_SOCK_TRUSTED on a socket opened without that capability. A local account can pass the socket to a setuid or CAP_NET_ADMIN program that invokes ioctl on an inherited descriptor, then pair unwanted devices, block pairing, read out-of-band data, or interrupt Bluetooth communication.
The record
- CVE
- CVE-2023-2002
- Published
- May 26, 2023
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-863, CWE-250, T1548.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 prior to Kernel 6.4-rc1
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.
Weakness, pattern, technique
Public exploit references
- Bluetooth power-state proof of conceptproof 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