CVE-2026-53259

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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:

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(high)
EPSS
2.5%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 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(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 34× in last 7d / 54× 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-06 23:59 UTCEG score recompute
  2. 2026-07-06 23:59 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:45 UTCEG score recompute
  6. 2026-07-06 11:45 UTCGHSA enrichment
  7. 2026-07-05 23:29 UTCEG score recompute
  8. 2026-07-05 23:29 UTCGHSA enrichment
  9. 2026-07-05 11:16 UTCEG score recompute
  10. 2026-07-05 11:16 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 22:59 UTCEG score recompute
  14. 2026-07-04 22:59 UTCGHSA enrichment
  15. 2026-07-04 10:46 UTCEG score recompute
  16. 2026-07-04 10:46 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 22:22 UTCEG score recompute
  20. 2026-07-03 22:22 UTCGHSA enrichment
  21. 2026-07-03 10:09 UTCEG score recompute
  22. 2026-07-03 10:09 UTCGHSA enrichment
  23. 2026-07-02 21:51 UTCEG score recompute
  24. 2026-07-02 21:50 UTCGHSA enrichment
  25. 2026-07-02 09:37 UTCEG score recompute
Show 29 more
  1. 2026-07-02 09:37 UTCGHSA enrichment
  2. 2026-07-01 21:24 UTCEG score recompute
  3. 2026-07-01 21:24 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 09:11 UTCEG score recompute
  6. 2026-07-01 09:11 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 20:58 UTCEG score recompute
  9. 2026-06-30 20:58 UTCGHSA enrichment
  10. 2026-06-30 08:45 UTCEG score recompute
  11. 2026-06-30 08:45 UTCGHSA enrichment
  12. 2026-06-29 20:32 UTCEG score recompute
  13. 2026-06-29 20:32 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 08:19 UTCEG score recompute
  17. 2026-06-29 08:19 UTCGHSA enrichment
  18. 2026-06-28 20:06 UTCEG score recompute
  19. 2026-06-28 20:06 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 07:52 UTCEG score recompute 7.80
  22. 2026-06-28 07:52 UTCGHSA enrichment
  23. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 10:05 UTCEG score recompute
  29. 2026-06-25 10:04 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 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-53259 actively exploited?
CVE-2026-53259 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53259?
CVE-2026-53259 has a CVSS v3 base score of 7.8 (NVD).
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

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