CVE-2026-93783

Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame

N/A
Published: September 24, 2026 at 04:02 PM UTC
Updated: October 3, 2026 at 11:17 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: validate skb length in rfcomm_recv_frame rfcomm_recv_frame() casts skb->data to struct rfcomm_hdr and dereferences hdr->addr and hdr->ctrl without validating skb->len first. A truncated frame with skb->len less than the minimum header size causes an out-of-bounds read of uninitialized memory. Additionally, a zero-length frame causes skb->len-- to underflow to UINT_MAX, making skb_tail_pointer() read far past the buffer. Commit 23882b828c3c ("Bluetooth: RFCOMM: validate skb length in MCC handlers") fixed the same class of missing-length-check bugs in the MCC sub-handlers, but the top-level rfcomm_recv_frame() was left unfixed. KMSAN reports: BUG: KMSAN: uninit-value in rfcomm_run ... Uninit was created at: __alloc_skb+0x474/0xb60 vhci_write+0xe9/0x870 Fix this by rejecting frames smaller than sizeof(struct rfcomm_hdr) + 1 (the minimum frame must have a 3-byte header and a 1-byte FCS).

Affected

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

2.6.12 ≤ v < 5.10.2712.6.12 ≤ v < 5.15.2222.6.12 ≤ v < 6.1.1892.6.12 ≤ v < 6.12.1112.6.12 ≤ v < 6.18.532.6.12 ≤ v < 6.6.1582.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 30d1d9f3495463f7c026e4c553127f79b486fcd6 (fixed)
Vendor states this is fixed in 3829af5fab5a22405bf1e7d69068c2ec0fce46ca (fixed)
Vendor states this is fixed in 67dc3b40fae71b6b11c71e7ff69bac0758818c05 (fixed)
Vendor states this is fixed in b161eacd7fa4a2d765724b5504ac6cc388e48f80 (fixed)
Vendor states this is fixed in b230e5bf501c5edaf2eb0991cb862ac142031d4b (fixed)
Vendor states this is fixed in bbc310caa2b6bf5fe42896ba27da0fbc12e4ac51 (fixed)
Vendor states this is fixed in fb40eda15122f6b780228639c1ead6820340ff54 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (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