Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-35967 Overview
CVE-2024-35967 is an out-of-bounds read vulnerability in the Linux kernel's Bluetooth Synchronous Connection-Oriented (SCO) socket implementation. The flaw resides in sco_sock_setsockopt() within net/bluetooth/sco.c, which copies data from user space without validating the input length. A local user with permission to open a Bluetooth SCO socket can trigger a slab-out-of-bounds read, as reported by syzbot through KASAN instrumentation. The issue affects multiple stable Linux kernel branches, as well as Debian GNU/Linux distributions that ship vulnerable kernels [CWE-125].
Critical Impact
Local attackers can trigger kernel memory out-of-bounds reads, potentially causing denial of service and leaking adjacent kernel heap contents to unprivileged processes.
Affected Products
- Linux kernel versions preceding the fix commits, including 6.9-rc1, 6.9-rc2, and 6.9-rc3
- Multiple maintained stable branches patched via backports to net/bluetooth/sco.c
- Debian GNU/Linux 10 (and other distributions shipping affected kernel builds)
Discovery Timeline
- 2024-05-20 - CVE-2024-35967 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2024-35967
Vulnerability Analysis
The defect lives in the SCO socket option handler sco_sock_setsockopt(). When processing user-supplied options, the function invokes copy_from_sockptr() (via copy_from_sockptr_offset() in include/linux/sockptr.h) using a fixed read size without first checking that the caller-provided optlen is large enough. KASAN flagged the condition with a slab-out-of-bounds report at net/bluetooth/sco.c:893, showing a 4-byte read beyond the allocated buffer.
Because the kernel reads memory past the boundary of the user-controlled option buffer in the slab allocator, adjacent heap data is dereferenced. Depending on heap layout and the specific socket option exercised, the resulting behavior ranges from kernel information disclosure to allocator corruption that destabilizes the system.
Root Cause
The root cause is missing input validation on the optlen argument supplied to setsockopt(2). The handler trusts the caller-provided length and copies the expected option size without clamping. This is a classic boundary check omission in a kernel syscall handler, categorized as an out-of-bounds read [CWE-125].
Attack Vector
Exploitation is local and requires the ability to open a Bluetooth SCO socket. An attacker calls setsockopt(2) on an SCO socket with an undersized optlen and a short option buffer, forcing the kernel to read past the allocation boundary. The vulnerability does not require elevated privileges beyond standard user capability to create Bluetooth sockets, which is why the attack complexity remains low on affected systems.
The fix adds explicit length validation before copy_from_sockptr() executes, rejecting undersized user input with -EINVAL. Refer to the upstream commits (for example kernel commit 7bc65d23ba20 and kernel commit 51eda36d33e4) for the exact patch content.
Detection Methods for CVE-2024-35967
Indicators of Compromise
- KASAN kernel log entries referencing slab-out-of-bounds in sco_sock_setsockopt or copy_from_sockptr_offset on systems built with memory sanitizers enabled.
- Unexpected kernel oops, panic, or Bluetooth stack instability following userspace activity that enumerates Bluetooth sockets.
- Processes without a legitimate Bluetooth role issuing setsockopt(2) calls against SCO sockets (AF_BLUETOOTH, BTPROTO_SCO).
Detection Strategies
- Audit host inventories for Linux kernels earlier than the fixed stable release versions referenced in the upstream commits.
- Monitor auditd or eBPF-based telemetry for socket(AF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO) followed by setsockopt() from unexpected user accounts.
- Correlate kernel ring buffer messages (dmesg) containing KASAN or general protection fault signatures with the originating process identifier.
Monitoring Recommendations
- Collect kernel logs centrally and alert on KASAN or BUG traces that reference net/bluetooth/sco.c.
- Track package inventory and patch state for linux-image-* on Debian systems against the Debian LTS announcement.
- For Siemens industrial assets, follow the Siemens Security Advisory SSA-265688 for platform-specific guidance.
How to Mitigate CVE-2024-35967
Immediate Actions Required
- Apply the vendor kernel update that includes the SCO setsockopt length validation patch to all affected Linux hosts.
- Where patching is delayed, unload or blacklist the Bluetooth kernel modules (bluetooth, bnep, btusb) on systems that do not require Bluetooth.
- Restrict local shell access on multi-user systems to limit the population of users capable of invoking Bluetooth syscalls.
Patch Information
Upstream fixes are available in multiple stable branches. Reference commits include 2c2dc87cdebe, 419a0ffca701, 51eda36d33e4, 72473db90900, 7bc65d23ba20, and b0e30c37695b. Debian users should install the kernel update described in the Debian LTS announcement.
Workarounds
- Blacklist the Bluetooth stack on systems that do not need it by adding blacklist bluetooth to /etc/modprobe.d/ and rebooting.
- Use seccomp or AppArmor profiles to deny socket(AF_BLUETOOTH, ...) for services that have no Bluetooth requirement.
- Disable the Bluetooth adapter and bluetooth.service on servers, workstations, and appliances where the radio is not in use.
# Configuration example: disable Bluetooth stack on affected hosts
sudo systemctl disable --now bluetooth.service
echo 'blacklist bluetooth' | sudo tee /etc/modprobe.d/disable-bluetooth.conf
echo 'blacklist btusb' | sudo tee -a /etc/modprobe.d/disable-bluetooth.conf
sudo modprobe -r btusb bluetooth 2>/dev/null || true
# Verify after reboot
lsmod | grep -E 'bluetooth|btusb' && echo 'Modules still loaded' || echo 'Bluetooth stack disabled'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

