CVE-2026-52919

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.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 tp_meter counter underflow during shutdown

batadv_tp_sender_shutdown() unconditionally decrements the "sending" atomic counter. If multiple paths (e.g. timeout, user cancel, and normal finish) call this function, the counter can underflow to -1.

Since the sender logic treats any non-zero value as "still sending", a negative value causes the sender kthread to loop indefinitely. This leads to a use-after-free when the interface is removed while the zombie thread is still active.

Fix this by using atomic_xchg() to ensure the counter only transitions from 1 to 0 once.

[sven: added missing change in batadv_tp_send]

CVSS v3
7.8
EG Score
7.8(high)
EPSS
1.9%
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 tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94f3b133168d1c49895e7cc6afbcf1cc0b354602
generic

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90ae3eae06b7b8ab9f6250b9497c860915b4c17b
generic

batman-adv: fix tp_meter counter underflow during shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01cefc5923889e29dbb5f281c3d457714ceb9c00

Vendor Advisories for CVE-2026-52919(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 53× in last 7d / 64× 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:13 UTCEG score recompute
  2. 2026-07-07 04:13 UTCVendor advisory
  3. 2026-07-07 04:12 UTCGHSA enrichment
  4. 2026-07-06 16:52 UTCEG score recompute
  5. 2026-07-06 16:52 UTCVendor advisory
  6. 2026-07-06 16:52 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 05:31 UTCEG score recompute
  10. 2026-07-06 05:31 UTCVendor advisory
  11. 2026-07-06 05:31 UTCGHSA enrichment
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 18:13 UTCEG score recompute
  15. 2026-07-05 18:13 UTCVendor advisory
  16. 2026-07-05 18:12 UTCGHSA enrichment
  17. 2026-07-05 06:54 UTCEG score recompute
  18. 2026-07-05 06:54 UTCVendor advisory
  19. 2026-07-05 06:54 UTCGHSA enrichment
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 19:35 UTCEG score recompute
  22. 2026-07-04 19:35 UTCVendor advisory
  23. 2026-07-04 19:35 UTCGHSA enrichment
  24. 2026-07-04 08:15 UTCEG score recompute
  25. 2026-07-04 08:15 UTCVendor advisory
Show 39 more
  1. 2026-07-04 08:14 UTCGHSA enrichment
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-03 20:55 UTCEG score recompute
  4. 2026-07-03 20:55 UTCVendor advisory
  5. 2026-07-03 20:55 UTCGHSA enrichment
  6. 2026-07-03 09:37 UTCEG score recompute
  7. 2026-07-03 09:37 UTCVendor advisory
  8. 2026-07-03 09:37 UTCGHSA enrichment
  9. 2026-07-02 22:19 UTCEG score recompute
  10. 2026-07-02 22:19 UTCVendor advisory
  11. 2026-07-02 22:19 UTCGHSA enrichment
  12. 2026-07-02 11:01 UTCEG score recompute
  13. 2026-07-02 11:01 UTCVendor advisory
  14. 2026-07-02 11:01 UTCGHSA enrichment
  15. 2026-07-01 23:39 UTCEG score recompute
  16. 2026-07-01 23:39 UTCVendor advisory
  17. 2026-07-01 23:39 UTCGHSA enrichment
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 12:18 UTCEG score recompute
  20. 2026-07-01 12:18 UTCVendor advisory
  21. 2026-07-01 12:18 UTCGHSA enrichment
  22. 2026-07-01 00:56 UTCEG score recompute
  23. 2026-07-01 00:56 UTCVendor advisory
  24. 2026-07-01 00:56 UTCGHSA enrichment
  25. 2026-06-30 23:22 UTCEPSS rescore
  26. 2026-06-30 13:38 UTCEG score recompute▲ 7.80
  27. 2026-06-30 13:38 UTCVendor advisory
  28. 2026-06-30 13:37 UTCGHSA enrichment
  29. 2026-06-28 14:07 UTCEPSS rescore
  30. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-27 11:09 UTCEG score recompute
  34. 2026-06-27 11:09 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-24 08:42 UTCEG score recompute
  39. 2026-06-24 08:40 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52919?
CVE-2026-52919 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix tp_meter counter underflow during shutdown batadvtpsender_shutdown() unconditionally decrements the "sending" atomic counter. If multiple paths (e.g. timeout, user cancel, and normal finish) call this function, the…
When was CVE-2026-52919 disclosed?
CVE-2026-52919 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-52919 actively exploited?
CVE-2026-52919 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52919?
CVE-2026-52919 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52919?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52919, 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-52919

Explore →

Is Your Infrastructure Affected by CVE-2026-52919?

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

Start Free Scan →Browse All CVEs