{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98103 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98103 is a vulnerability in Linux, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98103 and fix it if it is affected.\n\nWhat it is: CVE-2026-98103 is a vulnerability in Linux, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98103 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98103/ (Markdown: https://insights.sbomify.com/CVE-2026-98103/index.md)","id":"CVE-2026-98103","markdown":"https://insights.sbomify.com/CVE-2026-98103/index.md","name":"CVE-2026-98103","record":{"aliases":["AZL-104577","BELL-CVE-2026-98103","DEBIAN-CVE-2026-98103","GHSA-2hrc-mwqg-6fr2","UBUNTU-CVE-2026-98103"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel IGMP implementation can cause a deadlock, leading to denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nigmp: convert struct ip_sf_list to RCU\n\nCommit 23d2b94043ca (\"igmp: Add ip_mc_list lock in ip_check_mc_rcu\")\nadded spin_lock_bh(\u0026im-\u003elock) to ip_check_mc_rcu() to prevent a\nuse-after-free while iterating im-\u003esources during concurrent deletions.\n\nHowever, ip_check_mc_rcu() is called from RCU read-side critical\nsections in packet receive and route lookup fast paths (e.g.\n__mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()).\n\nWhen igmpv3_send_cr() or igmpv3_send_report() holds \u0026pmc-\u003elock and\ncalls add_grec() -\u003e igmpv3_newpack() -\u003e ip_route_output_ports(),\nan XFRM policy matching a multicast destination triggers\nxfrm_tmpl_resolve_one() -\u003e xfrm4_get_saddr() -\u003e __mkroute_output() -\u003e\nip_check_mc_rcu(). This attempts to acquire \u0026im-\u003elock while \u0026pmc-\u003elock\nis already held on the same CPU, triggering a lockdep recursive locking\nwarning / deadlock.\n\nFix this by converting IPv4 struct ip_sf_list to RCU, mirroring the\nIPv6 implementation in net/ipv6/mcast.c:\n\n1. Add struct rcu_head to struct ip_sf_list and annotate sf_next,\n   sources, and tomb as __rcu pointers.\n2. Use rcu_assign_pointer() and kfree_rcu() for list updates and\n   deletions.\n3. Remove spin_lock_bh(\u0026im-\u003elock) from ip_check_mc_rcu() and traverse\n   im-\u003esources locklessly with for_each_psf_rcu(), reading and writing\n   counter fields with READ_ONCE() and WRITE_ONCE().\n\nNote: RCU conversion of /proc/net/mcfilter will be done in a\nseparate patch.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"igmp: convert struct ip_sf_list to RCU","id":"CVE-2026-98103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted","id":"CVE-2026-98104"},"packages":[],"prev":{"headline":"ipv6: mcast: fix RCU list diversion in ip6_mc_del1_src()","id":"CVE-2026-98102"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel IGMP implementation can cause a deadlock, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-98103/"}