CVE-2026-98600

Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()

N/A
Published: October 18, 2026 at 03:19 PM UTC
Updated: October 19, 2026 at 10:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

30d1d9f3495463f7c026e4c553127f79b486fcd63829af5fab5a22405bf1e7d69068c2ec0fce46ca6.12.1116.18.5367dc3b40fae71b6b11c71e7ff69bac0758818c057.2b161eacd7fa4a2d765724b5504ac6cc388e48f80b230e5bf501c5edaf2eb0991cb862ac142031d4bbbc310caa2b6bf5fe42896ba27da0fbc12e4ac51fb40eda15122f6b780228639c1ead6820340ff54
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.55 (unaffected)
Vendor states this is fixed in 7.2.9 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card