CVE-2024-35966: Bluetooth: RFCOMM: Fix not validating setsockopt user input
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: Fix not validating setsockopt user input
syzbot reported rfcomm_sock_setsockopt_old() is copying data without
checking user input length.
BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset
include/linux/sockptr.h:49 [inline]
BUG: KASAN: slab-out-of-bounds in copy_from_sockptr
include/linux/sockptr.h:55 [inline]
BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt_old
net/bluetooth/rfcomm/sock.c:632 [inline]
BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt+0x893/0xa70
net/bluetooth/rfcomm/sock.c:673
Read of size 4 at addr ffff8880209a8bc3 by task syz-executor632/5064
Security readout for executives and security teams
Plain-English summary
CVE-2024-35966 is a Linux kernel Bluetooth RFCOMM bug where user-provided socket option data was copied without first checking its length. The reported failure is an out-of-bounds kernel read found by syzbot/KASAN. No CVSS score or confirmed active exploitation is provided in the source bundle.
Executive priority
Treat this as a scheduled but important kernel maintenance item, especially for Bluetooth-enabled endpoints, industrial systems, and embedded Linux assets. Escalate priority if a vendor advisory confirms affected deployed products or if Bluetooth is enabled on high-value systems.
Technical view
The flaw is in rfcomm_sock_setsockopt_old() within net/bluetooth/rfcomm/sock.c. copy_from_sockptr_offset/copy_from_sockptr could read past supplied data because the setsockopt input length was not validated. Linux stable commits are listed as fixes across multiple maintained kernel branches.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel versions with Bluetooth RFCOMM support available. The bundle also includes Debian LTS and Siemens advisories, indicating downstream packaging or product impact may exist, but specific affected Siemens products are not listed here.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, or weaponized exploit evidence. The bug was reported by syzbot with KASAN as a slab out-of-bounds read. Practical impact beyond local kernel memory-safety risk is not established by the provided sources.
Researcher notes
Evidence supports a missing input-length validation bug in Linux Bluetooth RFCOMM setsockopt handling. The source bundle lacks CVSS, CWE, exploitability analysis, and detailed downstream product matrices. Avoid assuming remote reachability or privilege impact without vendor or kernel maintainer confirmation.
Mitigation direction
Update affected Linux kernels to vendor-fixed stable releases.
Apply Debian LTS kernel updates where Debian systems are in scope.
Review Siemens advisory guidance for any Siemens-managed environments.
Disable or restrict Bluetooth/RFCOMM where business operations do not require it.
Track vendor advisories if running embedded or appliance Linux distributions.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and appliances.
Check whether Bluetooth and RFCOMM support are enabled or loadable.
Confirm installed kernels include the referenced stable fix commits.
Review Debian and vendor advisories for distribution-specific fixed packages.
Document exceptions where kernel updates require maintenance windows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35966 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.