CVE-2026-53259

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

ipv6: anycast: insert aca into global hash under idev->lock

syzbot reported a splat [1]: a slab-use-after-free in ipv6_chk_acast_addr(), which walks the global inet6_acaddr_lst[] hash under RCU and dereferences a struct ifacaddr6 that has already been freed while still linked in the hash, so a later reader walks into a dangling node.

In __ipv6_dev_ac_inc() the aca is allocated with refcount 1, then aca_get() bumps it to 2 to keep it alive across the unlocked region. It is published to idev->ac_list under idev->lock, but ipv6_add_acaddr_hash() runs after write_unlock_bh(). A concurrent teardown (ipv6_ac_destroy_dev() from addrconf_ifdown(), under RTNL) can slip into that window:

CPU0 __ipv6_dev_ac_inc CPU1 ipv6_ac_destroy_dev (RTNL) ------------------------------ ------------------------------------ aca_alloc() refcnt 1 aca_get() refcnt 2 write_lock_bh(idev->lock) add aca to ac_list write_unlock_bh(idev->lock) write_lock_bh(idev->lock) pull aca off ac_list write_unlock_bh(idev->lock) ipv6_del_acaddr_hash(aca) hlist_del_init_rcu() is a no-op, aca is not in the hash yet aca_put() refcnt 2->1 ipv6_add_acaddr_hash(aca) aca now inserted into the hash aca_put() refcnt 1->0 call_rcu(aca_free_rcu) -> kfree(aca)

The hash removal becomes a no-op because the insertion has not happened yet, so once CPU0 inserts and drops the last reference, the aca is freed while still linked in inet6_acaddr_lst[], and readers dereference freed memory after the slab slot is reused.

This window opened once RTNL stopped serializing the join path against device teardown. Move ipv6_add_acaddr_hash() inside the idev->lock section so the ac_list and hash insertions are atomic with respect to teardown: a racing remover now either misses the aca entirely or finds it in both lists.

acaddr_hash_lock is now nested under idev->lock, which is acquired in softirq context, so switch all acaddr_hash_lock sites to spin_lock_bh() to avoid the irq lock inversion reported in [2].

[1] https://syzkaller.appspot.com/bug?extid=a01df04303c131efbf3a [2] https://lore.kernel.org/netdev/[email protected]/

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

ipv6: anycast: insert aca into global hash under idev->lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: anycast: insert aca into global hash under idev->lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: anycast: insert aca into global hash under idev->lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15be7e9fdbff831fb3e89b83cc337a4f85ad3310

Vendor Advisories for CVE-2026-53259(2)

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

Affected Packages

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

Frequently asked(5)

What is CVE-2026-53259?
CVE-2026-53259 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: anycast: insert aca into global hash under idev->lock syzbot reported a splat [1]: a slab-use-after-free in ipv6chkacastaddr(), which walks the global inet6acaddr_lst[] hash under RCU and dereferences a struct ifacaddr6 that…
When was CVE-2026-53259 disclosed?
CVE-2026-53259 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-53259 actively exploited?
CVE-2026-53259 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53259?
CVE-2026-53259 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53259?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53259, 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-53259

Explore →

Is Your Infrastructure Affected by CVE-2026-53259?

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