Answer in brief
CVE-2026-53254 records a High severity (CVSS 8.1) vulnerability in Bluetooth: RFCOMM: validate skb length in MCC handlers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53254 records a High severity (CVSS 8.1) vulnerability in Bluetooth: RFCOMM: validate skb length in MCC handlers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c15c7c2878957cbfed93bcc29c13fdace464254 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d637136ce89f9a2309b2c3502402ce400dab0ef || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <98377e6b1a1a56561ec66a181573ea2b61b2079e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3eabc6d47a0ad22b053329997aaf0ec1e581e392 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <23882b828c3c8c51d0c946446a396b10abb3b16b | 7c15c7c2878957cbfed93bcc29c13fdace464254, 0d637136ce89f9a2309b2c3502402ce400dab0ef, 98377e6b1a1a56561ec66a181573ea2b61b2079e, 1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c, 3eabc6d47a0ad22b053329997aaf0ec1e581e392, 08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997, 23882b828c3c8c51d0c946446a396b10abb3b16b |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c15c7c2878957cbfed93bcc29c13fdace464254 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d637136ce89f9a2309b2c3502402ce400dab0ef || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <98377e6b1a1a56561ec66a181573ea2b61b2079e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3eabc6d47a0ad22b053329997aaf0ec1e581e392 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <23882b828c3c8c51d0c946446a396b10abb3b16b | 7c15c7c2878957cbfed93bcc29c13fdace464254, 0d637136ce89f9a2309b2c3502402ce400dab0ef, 98377e6b1a1a56561ec66a181573ea2b61b2079e, 1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c, 3eabc6d47a0ad22b053329997aaf0ec1e581e392, 08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997, 23882b828c3c8c51d0c946446a396b10abb3b16b |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.