CVE-2026-98099

ipv6: mcast: use rcu_assign_pointer() for __rcu list updates

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: use rcu_assign_pointer() for __rcu list updates Several places in net/ipv6/mcast.c update RCU-protected lists (np->ipv6_mc_list, idev->mc_list, idev->mc_tomb) using direct pointer assignments instead of rcu_assign_pointer(): 1. In __ipv6_dev_mc_dec(), unlinking a group from idev->mc_list did: *map = ma->next; without rcu_assign_pointer() while concurrent readers traverse idev->mc_list locklessly under rcu_read_lock(). 2. In ipv6_sock_mc_drop() and __ipv6_sock_mc_close(), unlinking a group from np->ipv6_mc_list directly assigned *lnk = mc_lst->next and np->ipv6_mc_list = mc_lst->next without rcu_assign_pointer(), racing with lockless readers in inet6_mc_check(). 3. In __ipv6_sock_mc_join(), mc_lst->next was initialized to np->ipv6_mc_list via raw assignment before publishing mc_lst. 4. In mld_del_delrec() and __ipv6_dev_mc_inc(), __rcu source pointers passed into rcu_assign_pointer() lacked explicit dereference helpers. Fix these by consistently using rcu_assign_pointer() along with mc_dereference() / sock_dereference().

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.091% likely to be exploited in the next 30 days, higher than 0.461% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 456b61bca8ee324ab6c18b065e632c9a8c88aa39 up to but excluding 0e3e3cec28c4d1bf29948da40b4e9e5d44f7852b (affected)
  • 456b61bca8ee324ab6c18b065e632c9a8c88aa39 up to but excluding 49d7e1b456ba2f3ee08b3e264d999c09992cde8e (affected)
  • 456b61bca8ee324ab6c18b065e632c9a8c88aa39 up to but excluding afca229b39acc2590976b3e4f6e0fe76cededc60 (affected)
  • 456b61bca8ee324ab6c18b065e632c9a8c88aa39 up to but excluding 2e46b0c9fcf7e10b64ce1630b925f47918d1f7f6 (affected)
  • 456b61bca8ee324ab6c18b065e632c9a8c88aa39 up to but excluding 0c8f56c583c3250408367880c98e4d6fbc929315 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.38 (affected)
  • 0 up to but excluding 2.6.38 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References