CVE-2026-98103igmp: convert struct ip_sf_list to RCU
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: igmp: convert struct ip_sf_list to RCU Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu") added spin_lock_bh(&im->lock) to ip_check_mc_rcu() to prevent a use-after-free while iterating im->sources during concurrent deletions. However, ip_check_mc_rcu() is called from RCU read-side critical sections in packet receive and route lookup fast paths (e.g. __mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()). When igmpv3_send_cr() or igmpv3_send_report() holds &pmc->lock and calls add_grec() -> igmpv3_newpack() -> ip_route_output_ports(), an XFRM policy matching a multicast destination triggers xfrm_tmpl_resolve_one() -> xfrm4_get_saddr() -> __mkroute_output() -> ip_check_mc_rcu(). This attempts to acquire &im->lock while &pmc->lock is already held on the same CPU, triggering a lockdep recursive locking warning / deadlock. Fix this by converting IPv4 struct ip_sf_list to RCU, mirroring the IPv6 implementation in net/ipv6/mcast.c: 1. Add struct rcu_head to struct ip_sf_list and annotate sf_next, sources, and tomb as __rcu pointers. 2. Use rcu_assign_pointer() and kfree_rcu() for list updates and deletions. 3. Remove spin_lock_bh(&im->lock) from ip_check_mc_rcu() and traverse im->sources locklessly with for_each_psf_rcu(), reading and writing counter fields with READ_ONCE() and WRITE_ONCE(). Note: RCU conversion of /proc/net/mcfilter will be done in a separate patch.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Undergoing Analysis
- Record last updated
- Sep 25, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 23d2b94043ca8835bd1e67749020e839f396a1c2 before f5182dfad54277267a8cb0c004a9cd4cf35aeebb; from 23d2b94043ca8835bd1e67749020e839f396a1c2 before d3011d1f293478c730aa0870490afa145c37600e; from 23d2b94043ca8835bd1e67749020e839f396a1c2 before e3206419bdb04e2087d8cc6be324df8639b3fac5; from 23d2b94043ca8835bd1e67749020e839f396a1c2 before 2987ee196c88dbde0463dc87d5fb209c684e34a2; b24065948ae6c48c9e20891f8cfe9850f1d748be; e9924c4204ede999b0515fd31a370a1e27f676bc; 78967749984cf3614de346c90f3e259ff8272735; 4768973dffed4d0126854514335ed4fe87bec1ab; and 12 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/f5182dfad54277267a8cb0c004a9cd4cf35aeebb
- https://git.kernel.org/stable/c/d3011d1f293478c730aa0870490afa145c37600e
- https://git.kernel.org/stable/c/e3206419bdb04e2087d8cc6be324df8639b3fac5
- https://git.kernel.org/stable/c/2987ee196c88dbde0463dc87d5fb209c684e34a2
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.