Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53254, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Modified3.1High8.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 80% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7c15c7c2878957cbfed93bcc29c13fdace464254
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0d637136ce89f9a2309b2c3502402ce400dab0ef
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 98377e6b1a1a56561ec66a181573ea2b61b2079e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3eabc6d47a0ad22b053329997aaf0ec1e581e392
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 23882b828c3c8c51d0c946446a396b10abb3b16b
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53254 badge
[![CVE-2026-53254](https://cveledger.app/badge/CVE-2026-53254.svg)](https://cveledger.app/cve/CVE-2026-53254)

Record last updated .