CVE-2026-53254: Bluetooth: RFCOMM: validate skb length in MCC handlers
Bluetooth: RFCOMM: validate skb length in MCC handlers
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1 - Configuration
In the RFCOMM MCC handlers, use skb_pull_data() to validate and access required data before casting skb->data to protocol-specific structs; ensure full struct validation is gated so it only occurs when skb->len indicates sufficient length (and validate only the DLCI byte first).
Linux kernel RFCOMM (MCC handlers) skb length validation before dereferencing protocol-specific structs = validate skb length using skb_pull_data() - Configuration
In rfcomm_recv_rpn(), add special handling for ETSI TS 07.10 truncated MCC frames by validating skb->len before dereferencing fields to prevent out-of-bounds reads.
Linux kernel rfcomm_recv_rpn() MCC frame length validation = validate skb->len before accessing fields / special handling for truncated frames
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53254?
CVE-2026-53254 has a risk rating of 29.
How do I fix CVE-2026-53254?
To fix CVE-2026-53254, update your Linux kernel to the latest version where this vulnerability is resolved.
What type of attack does CVE-2026-53254 allow?
CVE-2026-53254 enables remote attackers to send truncated MCC frames, potentially leading to denial of service.
Which software versions are affected by CVE-2026-53254?
CVE-2026-53254 affects certain versions of the Linux kernel that implement Bluetooth RFCOMM protocol.
When was CVE-2026-53254 published?
CVE-2026-53254 was published on June 25, 2026.