CVE-2026-53254: Bluetooth: RFCOMM: validate skb length in MCC handlers

Published Jun 25, 2026
·
Updated

Bluetooth: RFCOMM: validate skb length in MCC handlers

Affected Software

19 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.141.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=2.6.12.1<5.15.210
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.6.143
Linux Linux kernel>=6.7<6.12.94
Linux Linux kernel>=6.13<6.18.36
Linux Linux kernel>=6.19<7.0.13
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1
  2. 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()
  3. 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

Jun 25, 2026
CVE Published
via MITRE·08:39 AM
Data Sourced
via MITRE·08:39 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:09 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-53254?

CVE-2026-53254 has a risk rating of 29.

2

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.

3

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.

4

Which software versions are affected by CVE-2026-53254?

CVE-2026-53254 affects certain versions of the Linux kernel that implement Bluetooth RFCOMM protocol.

5

When was CVE-2026-53254 published?

CVE-2026-53254 was published on June 25, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203