CVE-2026-64572

ipv4: fib: free fib_alias with kfree_rcu() on insert error path

N/A
Published: August 5, 2026 at 08:08 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: free fib_alias with kfree_rcu() on insert error path fib_table_insert() publishes new_fa into the leaf's fa_list with fib_insert_alias() before calling the fib entry notifiers. When a notifier fails, the error path removes new_fa with fib_remove_alias() (hlist_del_rcu) and frees it right away with kmem_cache_free(). fib_table_lookup() walks that list under rcu_read_lock() only, so a concurrent lookup that already reached new_fa keeps reading it after the free: BUG: KASAN: slab-use-after-free in fib_table_lookup (net/ipv4/fib_trie.c:1601) Read of size 1 at addr ffff88810676d4eb by task exploit/297 Call Trace: fib_table_lookup (net/ipv4/fib_trie.c:1601) ip_route_output_key_hash_rcu (net/ipv4/route.c:2814) ip_route_output_key_hash (net/ipv4/route.c:2705) __ip4_datagram_connect (net/ipv4/datagram.c:49) udp_connect (net/ipv4/udp.c:2144) __sys_connect (net/socket.c:2167) __x64_sys_connect (net/socket.c:2173) do_syscall_64 entry_SYSCALL_64_after_hwframe which belongs to the cache ip_fib_alias of size 56 Triggering the error path needs CAP_NET_ADMIN and a registered fib notifier that can reject a route; a netdevsim device whose IPv4 FIB resource is exhausted is enough. Free new_fa with alias_free_mem_rcu(), as fib_table_delete() already does for a fib_alias removed from the trie.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 5.10.2655.6 ≤ v < 5.15.2165.6 ≤ v < 6.1.1835.6 ≤ v < 6.12.1015.6 ≤ v < 6.18.425.6 ≤ v < 6.6.1485.6 ≤ v < 7.1.65.6 ≤ v < 7.25.6a6c76c17df021b141b0d306828c9fe4ba2d2717c
Vendor states this is fixed in 6429c9cfd941e62acd7bb0bc64d631574d4c3b2a (fixed)
Vendor states this is fixed in 8150b5365f026e72250cacc527ea00be30f40105 (fixed)
Vendor states this is fixed in 9d0778571def598c31e84a38ae5a7ebc6f65e6d8 (fixed)
Vendor states this is fixed in b8d2ea75c76abcd0d72679c2f488271f573e32fb (fixed)
Vendor states this is fixed in bb03350f974aec352b660d032a1d283eb462165a (fixed)
Vendor states this is fixed in cb8be318b4432abd88d3172ec157330f27a5f7a7 (fixed)
Vendor states this is fixed in d007056868723de9c0cc3f5ffaad47a8d468b9a4 (fixed)
Vendor states this is fixed in f2f152e94a67bc746afaf05a1b2702c195553112 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card