CVE-2026-53254

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98377e6b1a1a56561ec66a181573ea2b61b2079e
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c15c7c2878957cbfed93bcc29c13fdace464254
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3eabc6d47a0ad22b053329997aaf0ec1e581e392
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23882b828c3c8c51d0c946446a396b10abb3b16b
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d637136ce89f9a2309b2c3502402ce400dab0ef
generic

Bluetooth: RFCOMM: validate skb length in MCC handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997

Vendor Advisories for CVE-2026-53254(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 316 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:37 UTCEG score recompute
  11. 2026-08-30 19:37 UTCVendor advisory
  12. 2026-08-30 19:37 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 23:57 UTCEG score recompute
  17. 2026-08-27 23:57 UTCVendor advisory
  18. 2026-08-27 23:57 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 00:14 UTCEG score recompute
  23. 2026-08-25 00:14 UTCVendor advisory
  24. 2026-08-25 00:14 UTCGHSA enrichment
  25. 2026-08-24 13:12 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:12 UTCVendor advisory
  2. 2026-08-24 13:12 UTCGHSA enrichment
  3. 2026-08-23 20:30 UTCVendor advisory
  4. 2026-08-23 20:30 UTCGHSA enrichment
  5. 2026-08-23 09:28 UTCEG score recompute
  6. 2026-08-23 09:28 UTCVendor advisory
  7. 2026-08-23 09:28 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 22:27 UTCVendor advisory
  10. 2026-08-22 22:27 UTCGHSA enrichment
  11. 2026-08-22 10:40 UTCEG score recompute
  12. 2026-08-22 10:40 UTCVendor advisory
  13. 2026-08-22 10:40 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 17:26 UTCGHSA enrichment
  16. 2026-08-21 05:20 UTCEG score recompute
  17. 2026-08-21 05:20 UTCVendor advisory
  18. 2026-08-21 05:20 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 18:14 UTCVendor advisory
  21. 2026-08-20 18:14 UTCGHSA enrichment
  22. 2026-08-20 07:06 UTCEG score recompute
  23. 2026-08-20 07:06 UTCVendor advisory
  24. 2026-08-20 07:05 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-19 12:40 UTCVendor advisory
  27. 2026-08-19 12:40 UTCGHSA enrichment
  28. 2026-08-19 01:31 UTCEG score recompute
  29. 2026-08-19 01:31 UTCVendor advisory
  30. 2026-08-19 01:31 UTCGHSA enrichment
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 12:53 UTCVendor advisory
  34. 2026-08-17 12:53 UTCGHSA enrichment
  35. 2026-08-17 01:51 UTCEG score recompute
  36. 2026-08-17 01:51 UTCVendor advisory
  37. 2026-08-17 01:51 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 14:49 UTCVendor advisory
  40. 2026-08-16 14:49 UTCGHSA enrichment
  41. 2026-08-16 03:47 UTCEG score recompute
  42. 2026-08-16 03:47 UTCVendor advisory
  43. 2026-08-16 03:47 UTCGHSA enrichment
  44. 2026-08-16 02:14 UTCEPSS rescore
  45. 2026-08-15 16:45 UTCVendor advisory
  46. 2026-08-15 16:45 UTCGHSA enrichment
  47. 2026-08-15 05:43 UTCEG score recompute
  48. 2026-08-15 05:43 UTCVendor advisory
  49. 2026-08-15 05:43 UTCGHSA enrichment
  50. 2026-08-15 01:30 UTCEPSS rescore
  51. 2026-08-14 18:41 UTCVendor advisory
  52. 2026-08-14 18:41 UTCGHSA enrichment
  53. 2026-08-14 07:37 UTCEG score recompute
  54. 2026-08-14 07:37 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 20:35 UTCVendor advisory
  57. 2026-08-13 20:35 UTCGHSA enrichment
  58. 2026-08-13 09:33 UTCVendor advisory
  59. 2026-08-13 09:33 UTCGHSA enrichment
  60. 2026-08-12 22:31 UTCEG score recompute
  61. 2026-08-12 22:31 UTCGHSA enrichment
  62. 2026-08-12 13:51 UTCEPSS rescore
  63. 2026-08-12 11:30 UTCVendor advisory
  64. 2026-08-12 11:30 UTCGHSA enrichment
  65. 2026-08-12 00:28 UTCEG score recompute
  66. 2026-08-12 00:28 UTCVendor advisory
  67. 2026-08-12 00:28 UTCGHSA enrichment
  68. 2026-08-11 13:26 UTCVendor advisory
  69. 2026-08-11 13:26 UTCGHSA enrichment
  70. 2026-08-11 02:24 UTCEG score recompute
  71. 2026-08-11 02:24 UTCVendor advisory
  72. 2026-08-11 02:24 UTCGHSA enrichment
  73. 2026-08-11 00:00 UTCEPSS rescore
  74. 2026-08-10 15:23 UTCGHSA enrichment
  75. 2026-08-10 04:21 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53254?
CVE-2026-53254 is a high vulnerability published on June 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…
When was CVE-2026-53254 disclosed?
CVE-2026-53254 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53254 actively exploited?
CVE-2026-53254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53254?
CVE-2026-53254 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53254?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53254, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53254

Explore →

Is Your Infrastructure Affected by CVE-2026-53254?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs