CVE-2026-98103

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.

Package Linux Kernel
Published 2026-09-25
Last modified 2026-09-30
Patch available
Yes

Affected versions

Linux kernel versions 4.4.284, 4.9.283, 4.14.247, 4.19.207, 5.4.145, 5.10.64, 5.13.16, 5.14.3, 5.15 and later are affected. Fixed in 6.12.111, 6.18.53, 7.2.7, 7.3-rc2 and their respective stable series.

Affected from
≥ 4.4.284 ≥ 4.9.283 ≥ 4.14.247 ≥ 4.19.207 ≥ 5.4.145 ≥ 5.10.64 ≥ 5.13.16 ≥ 5.14.3 ≥ 5.15
Fixed in
✓ 6.12.111 6.12.x ✓ 6.18.53 6.18.x ✓ 7.2.7 7.2.x ✓ 7.3-rc2

Frequently asked questions

  • What is CVE-2026-98103?

    CVE-2026-98103 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.4.284 onward and has been patched in 6.12.111, 6.18.53, 7.2.7 and others. CVE-2026-98103 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-98103?

    Yes. CVE-2026-98103 has been patched. Fixed versions include 6.12.111, 6.18.53, 7.2.7 and others. If you are running Linux kernel 4.4.284 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-98103 actively exploited?

    No. CVE-2026-98103 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.