CVE-2026-53254

Bluetooth: RFCOMM: validate skb length in MCC handlers

State
Published
Severity
8.1 High
Published
Jun 25, 2026
Updated
Oct 19, 2026
Reserved
Jun 9, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.18.1 HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HLinux

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 7c15c7c2878957cbfed93bcc29c13fdace464254Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 0d637136ce89f9a2309b2c3502402ce400dab0efAffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 98377e6b1a1a56561ec66a181573ea2b61b2079eAffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 1b070ac9e99c2c2c3a8112943ca98ab6fca7f10cAffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 3eabc6d47a0ad22b053329997aaf0ec1e581e392Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 23882b828c3c8c51d0c946446a396b10abb3b16bAffected
LinuxLinux
  • 2.6.12Affected
  • before 2.6.12Not affected
  • 5.15.210 through 5.15.*Not affected
  • 6.1.176 through 6.1.*Not affected
  • 6.6.143 through 6.6.*Not affected
  • 6.12.94 through 6.12.*Not affected
  • 6.18.36 through 6.18.*Not affected
  • 7.0.13 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.