CVE-2026-98103: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-2hrc-mwqg-6fr2
Share
Published
Advisory Summary

CVE-2026-98103 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98103 at a Glance

CVE Identifier CVE-2026-98103
GHSA Identifier GHSA-2hrc-mwqg-6fr2
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98103

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98103, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-98103 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98103
git.kernel.org/stable/c/2987ee196c... WEB
https://git.kernel.org/stable/c/2987ee196c88dbde0463dc87d5fb209c684e34a2
git.kernel.org/stable/c/d3011d1f29... WEB
https://git.kernel.org/stable/c/d3011d1f293478c730aa0870490afa145c37600e
git.kernel.org/stable/c/e3206419bd... WEB
https://git.kernel.org/stable/c/e3206419bdb04e2087d8cc6be324df8639b3fac5
git.kernel.org/stable/c/f5182dfad5... WEB
https://git.kernel.org/stable/c/f5182dfad54277267a8cb0c004a9cd4cf35aeebb

Frequently Asked Questions

What is CVE-2026-98103?
CVE-2026-98103 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98103?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98103?
CVE-2026-98103 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98103?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2hrc-mwqg-6fr2",
  "modified" : "2026-09-25T12:31:36Z",
  "published" : "2026-09-25T12:31:36Z",
  "aliases" : [ "CVE-2026-98103" ],
  "details" : "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(&im->lock) to ip_check_mc_rcu() to prevent a\nuse-after-free while iterating im->sources 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 &pmc->lock and\ncalls add_grec() -> igmpv3_newpack() -> ip_route_output_ports(),\nan XFRM policy matching a multicast destination triggers\nxfrm_tmpl_resolve_one() -> xfrm4_get_saddr() -> __mkroute_output() ->\nip_check_mc_rcu(). This attempts to acquire &im->lock while &pmc->lock\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(&im->lock) from ip_check_mc_rcu() and traverse\n   im->sources 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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98103"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2987ee196c88dbde0463dc87d5fb209c684e34a2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d3011d1f293478c730aa0870490afa145c37600e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e3206419bdb04e2087d8cc6be324df8639b3fac5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f5182dfad54277267a8cb0c004a9cd4cf35aeebb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:40Z"
  }
}