Skip to content

CVE-2026-99401 rtnetlink: wait for RCU readers in rtnl_link_unregister()

Unknown
Published
Updated
Exploit status
No public exploit known

Description

In the Linux kernel, the following vulnerability has been resolved:

rtnetlink: wait for RCU readers in rtnl_link_unregister()

rtnl_link_ops_get() finds ops on link_ops under rcu_read_lock() and only
then takes ops->srcu. rtnl_link_unregister() unlinks ops, then calls
synchronize_srcu() and cleanup_srcu_struct() without first waiting for
RCU readers. A reader that found ops before list_del_rcu() and has not yet
taken ops->srcu is not waited for.

Such a reader then locks a cleaned-up srcu_struct and keeps using ops
after the module that owns it is gone. rtnl_newlink() and
rtnl_dump_ifinfo() both look up ops without RTNL, the latter for any
user that dumps links filtered by kind.

With delays added between the lookup and srcu_read_lock() in
rtnl_link_ops_get(), and before rtnl_link_ops_put() in
rtnl_dump_ifinfo(), running "ip link show type dummy" alongside
"rmmod dummy" on a KASAN kernel gives:

BUG: KASAN: vmalloc-out-of-bounds in __srcu_read_unlock+0x57/0x70
Read of size 8 at addr ffffffffc02ff318 by task ip/147
Call Trace:
__srcu_read_unlock+0x57/0x70
rtnl_dump_ifinfo.cold+0x30/0x3b
rtnl_dumpit+0x7a/0x1b0
netlink_dump+0x486/0x11b0
__netlink_dump_start+0x661/0x910
rtnetlink_rcv_msg+0x611/0x9e0
netlink_rcv_skb+0x126/0x380
netlink_unicast+0x605/0x830
netlink_sendmsg+0x6d0/0xbb0
__sys_sendto+0x335/0x3a0

Call synchronize_rcu() before synchronize_srcu(), as
rtnl_af_unregister() already does. This should be enough because
rtnl_link_ops_get() is the only RCU walker of link_ops, and it takes
ops->srcu before rcu_read_unlock(), so every reader that found ops is
covered by synchronize_srcu() once the RCU grace period ends. The extra
grace period only costs time at module unload.

Readers and the writer were serialized by RTNL until link_ops got its
own mutex, which is why the missing RCU wait did not matter before.

Affected products

ProductAffected versionsFixed in
Linux kernel >= 6b57ff21a3109b1dba2d286ff415463e6fb1fca3, < 9e3a6b707681a6291a410d1b7ce15840a9912a86 9e3a6b707681a6291a410d1b7ce15840a9912a86
Linux kernel >= 6b57ff21a3109b1dba2d286ff415463e6fb1fca3, < ee636421740bc47e9d9e612ca7c9fa7dc5d17be1 ee636421740bc47e9d9e612ca7c9fa7dc5d17be1
Linux kernel >= 6b57ff21a3109b1dba2d286ff415463e6fb1fca3, < 3b70edea393de445255da6c706eebb823117a955 3b70edea393de445255da6c706eebb823117a955
Linux kernel = 6.13 No fix listed
Linux kernel < 6.18.61 6.18.61
Linux kernel < 7.3.2 7.3.2
Linux kernel < 7.4-rc1 7.4-rc1

References