CVE-2026-53254

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 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(high)
EPSS
20.2%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 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(2)

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

Data Freshness Timeline

(refreshed 58× in last 7d / 80× 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.

  1. 2026-07-07 02:35 UTCEG score recompute
  2. 2026-07-07 02:35 UTCVendor advisory
  3. 2026-07-07 02:35 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 15:33 UTCEG score recompute
  7. 2026-07-06 15:33 UTCVendor advisory
  8. 2026-07-06 15:32 UTCGHSA enrichment
  9. 2026-07-06 04:29 UTCEG score recompute
  10. 2026-07-06 04:29 UTCVendor advisory
  11. 2026-07-06 04:29 UTCGHSA enrichment
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 17:27 UTCEG score recompute
  15. 2026-07-05 17:27 UTCVendor advisory
  16. 2026-07-05 17:27 UTCGHSA enrichment
  17. 2026-07-05 06:25 UTCEG score recompute
  18. 2026-07-05 06:25 UTCVendor advisory
  19. 2026-07-05 06:24 UTCGHSA enrichment
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 19:19 UTCEG score recompute
  23. 2026-07-04 19:19 UTCVendor advisory
  24. 2026-07-04 19:18 UTCGHSA enrichment
  25. 2026-07-04 08:15 UTCEG score recompute
Show 55 more
  1. 2026-07-04 08:15 UTCVendor advisory
  2. 2026-07-04 08:15 UTCGHSA enrichment
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-03 21:13 UTCEG score recompute
  6. 2026-07-03 21:13 UTCVendor advisory
  7. 2026-07-03 21:13 UTCGHSA enrichment
  8. 2026-07-03 10:11 UTCEG score recompute
  9. 2026-07-03 10:11 UTCVendor advisory
  10. 2026-07-03 10:11 UTCGHSA enrichment
  11. 2026-07-02 23:09 UTCEG score recompute
  12. 2026-07-02 23:09 UTCVendor advisory
  13. 2026-07-02 23:09 UTCGHSA enrichment
  14. 2026-07-02 12:07 UTCEG score recompute
  15. 2026-07-02 12:07 UTCVendor advisory
  16. 2026-07-02 12:07 UTCGHSA enrichment
  17. 2026-07-02 01:04 UTCEG score recompute
  18. 2026-07-02 01:04 UTCVendor advisory
  19. 2026-07-02 01:04 UTCGHSA enrichment
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 14:03 UTCEG score recompute
  22. 2026-07-01 14:03 UTCVendor advisory
  23. 2026-07-01 14:02 UTCGHSA enrichment
  24. 2026-07-01 03:00 UTCEG score recompute
  25. 2026-07-01 03:00 UTCVendor advisory
  26. 2026-07-01 03:00 UTCGHSA enrichment
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 15:58 UTCEG score recompute
  29. 2026-06-30 15:58 UTCVendor advisory
  30. 2026-06-30 15:57 UTCGHSA enrichment
  31. 2026-06-30 04:54 UTCEG score recompute
  32. 2026-06-30 04:54 UTCVendor advisory
  33. 2026-06-30 04:54 UTCGHSA enrichment
  34. 2026-06-29 17:36 UTCEG score recompute
  35. 2026-06-29 17:36 UTCVendor advisory
  36. 2026-06-29 17:35 UTCGHSA enrichment
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-29 06:31 UTCEG score recompute
  40. 2026-06-29 06:31 UTCVendor advisory
  41. 2026-06-29 06:31 UTCGHSA enrichment
  42. 2026-06-28 19:29 UTCEG score recompute
  43. 2026-06-28 19:29 UTCVendor advisory
  44. 2026-06-28 19:29 UTCGHSA enrichment
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 08:27 UTCEG score recompute 8.10
  47. 2026-06-28 08:27 UTCVendor advisory
  48. 2026-06-28 08:26 UTCGHSA enrichment
  49. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  50. 2026-06-28 04:56 UTCEPSS rescore
  51. 2026-06-28 04:56 UTCEPSS rescore
  52. 2026-06-27 03:08 UTCEPSS rescore
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-25 10:07 UTCEG score recompute
  55. 2026-06-25 10:06 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 June 30, 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 20.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53254?
CVE-2026-53254 has a CVSS v3 base score of 8.1 (NVD).
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

Explore the affected products and dependency analysis for 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.