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

Published Nov 19, 2026
·
Updated

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

rtnetlink: wait for RCU readers in rtnllinkunregister()

rtnllinkopsget() finds ops on linkops under rcureadlock() and only then takes ops->srcu. rtnllinkunregister() unlinks ops, then calls synchronizesrcu() and cleanupsrcustruct() without first waiting for RCU readers. A reader that found ops before listdelrcu() and has not yet taken ops->srcu is not waited for.

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

With delays added between the lookup and srcureadlock() in rtnllinkopsget(), and before rtnllinkopsput() in rtnldumpifinfo(), running "ip link show type dummy" alongside "rmmod dummy" on a KASAN kernel gives:

BUG: KASAN: vmalloc-out-of-bounds in srcureadunlock+0x57/0x70 Read of size 8 at addr ffffffffc02ff318 by task ip/147 Call Trace: srcureadunlock+0x57/0x70 rtnldumpifinfo.cold+0x30/0x3b rtnldumpit+0x7a/0x1b0 netlinkdump+0x486/0x11b0 netlinkdumpstart+0x661/0x910 rtnetlinkrcvmsg+0x611/0x9e0 netlinkrcvskb+0x126/0x380 netlinkunicast+0x605/0x830 netlinksendmsg+0x6d0/0xbb0 syssendto+0x335/0x3a0

Call synchronizercu() before synchronizesrcu(), as rtnlafunregister() already does. This should be enough because rtnllinkopsget() is the only RCU walker of linkops, and it takes ops->srcu before rcureadunlock(), so every reader that found ops is covered by synchronizesrcu() 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 linkops got its own mutex, which is why the missing RCU wait did not matter before.

Affected Software

2 affected componentsFixes available
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  3. Compensating control

    In rtnl_link_unregister(), call synchronize_rcu() before synchronize_srcu() so RCU readers have finished before the SRCU cleanup.

Event History

Nov 19, 2026
CVE Published
via MITRE·02:23 PM
Data Sourced
via MITRE·02:23 PM
Description
Data Sourced
via OSV·02:23 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203