Bug 2492795 (CVE-2026-53254) - CVE-2026-53254 kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers
Summary: CVE-2026-53254 kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers
Keywords:
Status: NEW
Alias: CVE-2026-53254
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-25 10:06 UTC by OSIDB Bzimport
Modified: 2026-09-08 11:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:65334 0 None None None 2026-09-08 11:35:15 UTC

Description OSIDB Bzimport 2026-06-25 10:06:10 UTC
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: RFCOMM: validate skb length in MCC handlers

The RFCOMM MCC handlers cast skb->data to protocol-specific structs
without validating skb->len first. A malicious remote device can send
truncated MCC frames and trigger out-of-bounds reads in these handlers.

Fix this by using skb_pull_data() to validate and access the required
data before dereferencing it.

rfcomm_recv_rpn() requires special handling since ETSI TS 07.10 allows
1-byte RPN requests. Handle this by validating only the DLCI byte first,
and validating the full struct only when len > 1.

Comment 3 errata-xmlrpc 2026-09-08 11:35:14 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:65334 https://access.redhat.com/errata/RHSA-2026:65334


Note You need to log in before you can comment on or make changes to this bug.