CVE-2026-98099: ipv6: mcast: use rcu_assign_pointer() for __rcu list updates
In the Linux kernel, the following vulnerability has been resolved:
ipv6: mcast: use rcuassignpointer() for rcu list updates
Several places in net/ipv6/mcast.c update RCU-protected lists (np->ipv6mclist, idev->mclist, idev->mctomb) using direct pointer assignments instead of rcuassignpointer():
1. In ipv6devmcdec(), unlinking a group from idev->mclist did: map = ma->next; without rcuassignpointer() while concurrent readers traverse idev->mclist locklessly under rcureadlock(). 2. In ipv6sockmcdrop() and ipv6sockmcclose(), unlinking a group from np->ipv6mclist directly assigned lnk = mclst->next and np->ipv6mclist = mclst->next without rcuassignpointer(), racing with lockless readers in inet6mccheck(). 3. In ipv6sockmcjoin(), mclst->next was initialized to np->ipv6mclist via raw assignment before publishing mclst. 4. In mlddeldelrec() and ipv6devmcinc(), rcu source pointers passed into rcuassignpointer() lacked explicit dereference helpers.
Fix these by consistently using rcuassignpointer() along with mcdereference() / sockdereference().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In Linux kernel net/ipv6/mcast.c, replace direct assignments that update RCU-protected lists with rcu_assign_pointer(), including updates to np->ipv6_mc_list, idev->mc_list, and idev->mc_tomb in __ipv6_dev_mc_dec(), __ipv6_sock_mc_join(), ipv6_sock_mc_drop(), __ipv6_sock_mc_close(), mld_del_delrec(), and __ipv6_dev_mc_inc(); use explicit RCU dereference helpers for __rcu source pointers.
Event History
Frequently Asked Questions
What conditions are needed for this issue to occur?
The issue involves concurrent access to IPv6 multicast membership lists: one execution path updates or removes list entries while another traverses the same lists locklessly under RCU. The affected paths include IPv6 device multicast-group handling and IPv6 socket multicast join, drop, close, and membership-check operations.
How can I determine whether my system has the fix?
Check whether the kernel source or applied stable patches include the referenced commits 2e46b0c9fcf7e10b64ce1630b925f47918d1f7f6 or 0c8f56c583c3250408367880c98e4d6fbc929315. The corrected code uses rcu_assign_pointer() when publishing or unlinking the relevant __rcu list pointers, with mc_dereference() or sock_dereference() for source-pointer access.