CVE-2026-52914

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: 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:

batman-adv: fix fragment reassembly length accounting

batman-adv keeps a running payload length for queued fragments and uses it to validate a fragment chain before reassembly.

That accounting currently allows the accumulated fragment length to be truncated during updates. As a result, malformed fragment chains can bypass the intended validation and drive reassembly with inconsistent length state, leading to a local denial of service.

Fix the accounting by storing the accumulated length in a length-typed field and rejecting update overflows before the existing validation logic runs.

The fix was verified against the original reproducer and against valid fragment reassembly paths.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
40.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

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

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fdb2c96efb2baeb3725e9ce3ede8f1e36f5490f0
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f653b040dad1af70fa5cd4fe085e4758925480c9
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e910dbf509125fe51ad68e4fa74dc8ab0a8e787a
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4f3f6b818aa6a678bc54a2d4e0bece2303c6a64
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cd3f16c320bfdadd4509358122368deb56a5741
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/975563c5de1123dde1ec7946bf5556d20c89d74e
generic

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix fragment reassembly length accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37be61825b15534a16ff9cfc9546de155b6df982

Vendor Advisories for CVE-2026-52914(1)

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 82× in last 7d / 95× 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 04:42 UTCEG score recompute
  2. 2026-07-07 04:42 UTCGHSA enrichment
  3. 2026-07-07 00:23 UTCEG score recompute
  4. 2026-07-07 00:22 UTCGHSA enrichment
  5. 2026-07-06 20:05 UTCEG score recompute
  6. 2026-07-06 20:04 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 15:40 UTCEG score recompute
  10. 2026-07-06 15:40 UTCGHSA enrichment
  11. 2026-07-06 11:21 UTCEG score recompute
  12. 2026-07-06 11:21 UTCGHSA enrichment
  13. 2026-07-06 06:43 UTCEG score recompute
  14. 2026-07-06 06:43 UTCGHSA enrichment
  15. 2026-07-06 02:26 UTCEG score recompute
  16. 2026-07-06 02:26 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 22:09 UTCEG score recompute
  20. 2026-07-05 22:09 UTCGHSA enrichment
  21. 2026-07-05 17:53 UTCEG score recompute
  22. 2026-07-05 17:53 UTCGHSA enrichment
  23. 2026-07-05 13:36 UTCEG score recompute
  24. 2026-07-05 13:36 UTCGHSA enrichment
  25. 2026-07-05 09:19 UTCEG score recompute
Show 70 more
  1. 2026-07-05 09:19 UTCGHSA enrichment
  2. 2026-07-05 05:01 UTCEG score recompute
  3. 2026-07-05 05:01 UTCGHSA enrichment
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-05 00:42 UTCEG score recompute
  6. 2026-07-05 00:42 UTCGHSA enrichment
  7. 2026-07-04 20:25 UTCEG score recompute
  8. 2026-07-04 20:25 UTCGHSA enrichment
  9. 2026-07-04 16:09 UTCEG score recompute
  10. 2026-07-04 16:08 UTCGHSA enrichment
  11. 2026-07-04 11:47 UTCEG score recompute
  12. 2026-07-04 11:47 UTCGHSA enrichment
  13. 2026-07-04 07:28 UTCEG score recompute
  14. 2026-07-04 07:28 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 02:59 UTCEG score recompute
  17. 2026-07-04 02:59 UTCGHSA enrichment
  18. 2026-07-03 22:39 UTCEG score recompute
  19. 2026-07-03 22:39 UTCGHSA enrichment
  20. 2026-07-03 18:22 UTCEG score recompute
  21. 2026-07-03 18:22 UTCGHSA enrichment
  22. 2026-07-03 14:05 UTCEG score recompute
  23. 2026-07-03 14:05 UTCGHSA enrichment
  24. 2026-07-03 09:49 UTCEG score recompute
  25. 2026-07-03 09:48 UTCGHSA enrichment
  26. 2026-07-03 05:31 UTCEG score recompute
  27. 2026-07-03 05:31 UTCGHSA enrichment
  28. 2026-07-03 01:03 UTCEG score recompute
  29. 2026-07-03 01:03 UTCGHSA enrichment
  30. 2026-07-02 20:47 UTCEG score recompute
  31. 2026-07-02 20:47 UTCGHSA enrichment
  32. 2026-07-02 16:26 UTCEG score recompute
  33. 2026-07-02 16:26 UTCGHSA enrichment
  34. 2026-07-02 12:08 UTCEG score recompute
  35. 2026-07-02 12:07 UTCGHSA enrichment
  36. 2026-07-02 07:48 UTCEG score recompute
  37. 2026-07-02 07:48 UTCGHSA enrichment
  38. 2026-07-02 03:31 UTCEG score recompute
  39. 2026-07-02 03:31 UTCGHSA enrichment
  40. 2026-07-01 23:14 UTCEG score recompute
  41. 2026-07-01 23:14 UTCGHSA enrichment
  42. 2026-07-01 18:57 UTCEG score recompute
  43. 2026-07-01 18:57 UTCGHSA enrichment
  44. 2026-07-01 15:07 UTCEPSS rescore
  45. 2026-07-01 14:40 UTCEG score recompute
  46. 2026-07-01 14:40 UTCGHSA enrichment
  47. 2026-07-01 10:24 UTCEG score recompute
  48. 2026-07-01 10:24 UTCGHSA enrichment
  49. 2026-07-01 06:07 UTCEG score recompute
  50. 2026-07-01 06:07 UTCGHSA enrichment
  51. 2026-07-01 01:51 UTCEG score recompute
  52. 2026-07-01 01:51 UTCGHSA enrichment
  53. 2026-06-30 23:22 UTCEPSS rescore
  54. 2026-06-30 21:34 UTCEG score recompute
  55. 2026-06-30 21:34 UTCGHSA enrichment
  56. 2026-06-30 17:16 UTCEG score recompute 9.80
  57. 2026-06-30 17:16 UTCGHSA enrichment
  58. 2026-06-29 14:06 UTCEPSS rescore
  59. 2026-06-29 14:06 UTCEPSS rescore
  60. 2026-06-28 14:07 UTCEPSS rescore
  61. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  62. 2026-06-28 04:56 UTCEPSS rescore
  63. 2026-06-28 04:56 UTCEPSS rescore
  64. 2026-06-27 12:55 UTCEG score recompute
  65. 2026-06-27 12:55 UTCGHSA enrichment
  66. 2026-06-27 03:08 UTCEPSS rescore
  67. 2026-06-25 13:49 UTCEPSS rescore
  68. 2026-06-24 14:05 UTCEPSS rescore
  69. 2026-06-24 08:42 UTCEG score recompute
  70. 2026-06-24 08:40 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52914?
CVE-2026-52914 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix fragment reassembly length accounting batman-adv keeps a running payload length for queued fragments and uses it to validate a fragment chain before reassembly. That accounting currently allows the accumulated…
When was CVE-2026-52914 disclosed?
CVE-2026-52914 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52914 actively exploited?
CVE-2026-52914 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52914?
CVE-2026-52914 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52914?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52914, 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-52914

Explore →

Is Your Infrastructure Affected by CVE-2026-52914?

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