Bluetooth: HIDP: reject frames without a transaction header
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.266, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: reject frames without a transaction header hidp_recv_ctrl_frame() and hidp_recv_intr_frame() read skb->data[0] before checking that the L2CAP SDU contains a transaction header. A connected HIDP peer can send an empty basic-mode SDU and make both paths use an uninitialized byte from skb tailroom. KMSAN reports the use in hidp_session_run(), with the uninitialized value originating in __alloc_skb() through vhci_write(). The control path produces two reports and the interrupt path produces one. The byte can also be controlled by a malformed lower-layer packet. If an HCI ACL packet contains an L2CAP PDU with a declared zero-length payload followed by an extra 0x15 byte, l2cap_recv_acldata() reduces skb->len to the declared PDU length before dispatch. The current HIDP path nevertheless consumes the extra byte as HIDP_TRANS_HID_CONTROL | HIDP_CTRL_VIRTUAL_CABLE_UNPLUG and terminates the HIDP session. With this change, the same packet is discarded and a subsequent feature report request succeeds. Pull the transaction header with skb_pull_data() and discard frames that do not contain it.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 24c64ccd5c1fc9934b427335b0d976c7f2b1a7d8; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 238c333bc4b3f245c626632e8bfa3c9dab97f51b; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 567a2a0a633f2ea5fdccaf3517c09f22c9d860c7; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 46ca5ab39737d7c6f9ca77ecf714cdcfa6caaeec; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 97b61241ab45bfa5b0526cb0f3978942493bc811; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 2ebf63aa557a69990b4e9ea22be224d58aabce96; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 854194494a6f726a60b90b76059148bf08df023d; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 47778d2c2087b5d192398f6fddf692d16a5431cf
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.266; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.151; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8
References 8
git.kernel.org
- stable/c/24c64ccd5c1fc9934b427335b0d976c7f2b1a7d8
- stable/c/238c333bc4b3f245c626632e8bfa3c9dab97f51b
- stable/c/567a2a0a633f2ea5fdccaf3517c09f22c9d860c7
- stable/c/46ca5ab39737d7c6f9ca77ecf714cdcfa6caaeec
- stable/c/97b61241ab45bfa5b0526cb0f3978942493bc811
- stable/c/2ebf63aa557a69990b4e9ea22be224d58aabce96
- stable/c/854194494a6f726a60b90b76059148bf08df023d
- stable/c/47778d2c2087b5d192398f6fddf692d16a5431cf