CVE-2026-53259
ipv6: anycast: insert aca into global hash under idev->lock
Reported by linux · Published 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 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/6a194ef7.ba3b1513.1890b4.0000.GAE@google.com/
EPSS 0.12% · 1.6th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| rtla | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-core | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-debug-modules | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| rv | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-zfcpdump-modules | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-rt | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-modules-extra-matched | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-rt-debug | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-debug-debuginfo | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-rt-64k | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| python3-perf | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
| kernel-rt-debug-debuginfo | errata.rockylinux.org | 6.12.0-211.52.1.el10 |
55 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | eb1ac9ff6c4a5720b1a1476233be374c5dc44bff, eb1ac9ff6c4a5720b1a1476233be374c5dc44bff, eb1ac9ff6c4a5720b1a1476233be374c5dc44bff |
| Linux | Linux | 6.17, 0, 6.18.36 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel-livepatch-6.18.36-69.134 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| chainguard | linux-gcp-6.18 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | perf6.18 | 0 |
| linux | linux_kernel | 6.17, 6.17, 6.17 |
| Linux | Linux | 7.1, *, * |
| chainguard | linux-qemu-melange | 0 |
| chainguard | linux-qemu-6.18 | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| chainguard | linux-azure-6.18 | 0 |
Timeline
- Jun 24, 2026 CVE Published
- Jun 26, 2026 EPSS Score (7 in total, the first dated here)
- Jun 26, 2026 Coalition ESS Score
- Jun 29, 2026 Security Advisory (64 in total, the first dated here)
- Jul 8, 2026 CVE Updated
- Aug 11, 2026 Distribution Patch (64 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-53259
vulnetix vdb fixes CVE-2026-53259
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-53259/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart