CVE-2026-98099ipv6: mcast: use rcu_assign_pointer() for __rcu list updates
- 4.7MediumCVSS base score
- 0.09%Exploitation in 30 daysEPSS · top 100% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
Published
- 26 days later
· 26 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.09% · top 100% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.
Affected products
- affected 456b61bca8ee324ab6c18b065e632c9a8c88aa39 – < 0e3e3cec28c4d1bf29948da40b4e9e5d44f7852b
- affected 456b61bca8ee324ab6c18b065e632c9a8c88aa39 – < 49d7e1b456ba2f3ee08b3e264d999c09992cde8e
- affected 456b61bca8ee324ab6c18b065e632c9a8c88aa39 – < afca229b39acc2590976b3e4f6e0fe76cededc60
- affected 456b61bca8ee324ab6c18b065e632c9a8c88aa39 – < 2e46b0c9fcf7e10b64ce1630b925f47918d1f7f6
- affected 456b61bca8ee324ab6c18b065e632c9a8c88aa39 – < 0c8f56c583c3250408367880c98e4d6fbc929315
- affected 2.6.38
- unaffected < 2.6.38
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0e3e3cec28c4d1bf29948da40b4e9e5d44f7852b (opens in a new tab)
- https://git.kernel.org/stable/c/49d7e1b456ba2f3ee08b3e264d999c09992cde8e (opens in a new tab)
- https://git.kernel.org/stable/c/afca229b39acc2590976b3e4f6e0fe76cededc60 (opens in a new tab)
- https://git.kernel.org/stable/c/2e46b0c9fcf7e10b64ce1630b925f47918d1f7f6 (opens in a new tab)
- https://git.kernel.org/stable/c/0c8f56c583c3250408367880c98e4d6fbc929315 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86929 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98099)Record last updated .