Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 15be7e9fdbff831fb3e89b83cc337a4f85ad3310, 3a967c498baa976b11d4800dda224c507416e97c, f723ccaff2fb72b71ae8a9fd283f0dee4d9ae7a3.

Low priority for now. Upgrade to Linux Linux 15be7e9fdbff831fb3e89b83cc337a4f85ad3310, 3a967c498baa976b11d4800dda224c507416e97c, f723ccaff2fb72b71ae8a9fd283f0dee4d9ae7a3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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/

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Aug 5, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53259

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.17 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.17affected
    • eb1ac9ff6c4a5720b1a1476233be374c5dc44bff and later · before 15be7e9fdbff831fb3e89b83cc337a4f85ad3310affected · git
    • eb1ac9ff6c4a5720b1a1476233be374c5dc44bff and later · before 3a967c498baa976b11d4800dda224c507416e97caffected · git
    • eb1ac9ff6c4a5720b1a1476233be374c5dc44bff and later · before f723ccaff2fb72b71ae8a9fd283f0dee4d9ae7a3affected · git
    • before 6.17not affected · semver
    • 6.18.36 and later · up to and including 6.18.*not affected · semver
    • 7.0.13 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:14linuxbefore 7.0.13-17.0.13-1
Red Hat:enterprise_linux:10.2kernelbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64kbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debugbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-debuginfobefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-develbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-devel-matchedbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modulesbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modules-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modules-extrabefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debuginfobefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-develbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-devel-matchedbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modulesbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modules-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modules-extrabefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-abi-stablelistsbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debugbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debug-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debug-debuginfobefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debug-develbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2

+68

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53251Jun 25, 2026 · Bluetooth: ISO: Fix not releasing hdev reference on iso_conn_big_sync
    22Monitor
  • ← EarlierCVE-2026-53252Jun 25, 2026 · Bluetooth: fix memory leak in error path of hci_alloc_dev()
    22Monitor
  • Later →CVE-2026-53261Jun 25, 2026 · devlink: Release nested relation on devlink free
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux15be7e9fdbff831fb3e89b83cc337a4f85ad3310Vendor (CNA)
Linux Linux3a967c498baa976b11d4800dda224c507416e97cVendor (CNA)
Linux Linuxf723ccaff2fb72b71ae8a9fd283f0dee4d9ae7a3Vendor (CNA)
debian:linux7.0.13-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.52.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records