CVE-2026-98600: Linux
EPSS: 0.2% probability of exploitation activity in the next 30 days.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() While rfcomm_recv_frame() verifies that skb->len is at least sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame with an extended 2-byte length field (!__test_ea(hdr->len)) has a 4-byte header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2). When a 4-byte RFCOMM frame with EA == 0 arrives: 1. The initial skb->len < sizeof(*hdr) + 1 check passes (4 < 4 is false). 2. Trimming the FCS byte decrements skb->len to 3. 3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 > 3) and returns NULL without advancing skb->data. 4. Because the return value of skb_pull() is ignored, the un-pulled 3-byte struct rfcomm_hdr remains at skb->data and is either queued as application payload via rfcomm_recv_data() or parsed as a multiplexer control command via rfcomm_recv_mcc() on DLCI 0. Fix this by extending the length check in rfcomm_recv_frame() to also require skb->len >= sizeof(*hdr) + 2 when !__test_ea(hdr->len).
What to do
The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.
- Linux, from 6.12.111, before 6.12.112: fixed in 6.12.112
- Linux, from 6.18.53, before 6.18.55: fixed in 6.18.55
- Linux, from 7.2, before 7.2.9: fixed in 7.2.9
Affected products
- Linux Linux: from 6.12.111, before 6.12.112 (fixed in 6.12.112); from 6.18.53, before 6.18.55 (fixed in 6.18.55); from 7.2, before 7.2.9 (fixed in 7.2.9)
Published 2026-10-18. Last modified 2026-10-19.