CVE-2026-98098: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-vgfp-jj93-v4hf
Share
Published
Advisory Summary

CVE-2026-98098 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-98098 at a Glance

CVE Identifier CVE-2026-98098
GHSA Identifier GHSA-vgfp-jj93-v4hf
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-98098

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-98098, 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: tipc: fix NULL deref in tipc_named_node_up() on empty publication list User-space applications can bind a large number of service addresses to one or more sockets. Each binding of a local-scope service address inserts one entry (publication) into the TIPC name table. If the number of these publications exceeds TIPC_MAX_PUBL (65535), protocol service types (such as node state and link state) are no longer inserted into the name table. This causes two issues: 1. User-space applications subscribing to node or link up/down events stop receiving notifications. 2. A NULL pointer dereference can occur: BUG: kernel NULL pointer dereference, address: 00000000000000d0 ... CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc4-default+ #5 PREEMPT(full) ... RIP: 0010:tipc_named_node_up (./include/linux/skbuff.h:2251 net/tipc/name_distr.c:195 net/tipc/name_distr.c:221) ... Call Trace: <IRQ> tipc_node_write_unlock (net/tipc/node.c:428) tipc_rcv (net/tipc/node.c:934 net/tipc/node.c:2189) tipc_udp_recv (net/tipc/udp_media.c:389) Thread 1 (tipc_net_finalize) | Thread 2 (named_distribute) -----------------------------|----------------------------- | ... | list_for_each_entry(publ, pls, binding_node) { | ... | __skb_queue_tail(list, skb); | ... | } | ... | hdr = buf_msg(skb_peek_tail(list)); ... | tipc_nametbl_publish(); | If 'tipc_nametbl_publish()' (Thread 1) fails because the number of local publications reaches TIPC_MAX_PUBL, list (Thread 2) will be empty. As a result, NULL is passed to 'buf_msg()', leading to a NULL pointer dereference. Fix these issues by allowing protocol service types (node state, link state, and topology server) to be inserted into the name table unconditionally. This ensures that users subscribing to these types always receive notifications. In addition, the maximum number of local user publications is reduced to (TIPC_MAX_PUBL - 1). This ensures that the maximum bulk size calculated in tipc_link_set_queue_limits() remains valid.

References

NVD — CVE-2026-98098 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98098
git.kernel.org/stable/c/246a4b4aac... WEB
https://git.kernel.org/stable/c/246a4b4aace490664927042e93400a6f940d197f
git.kernel.org/stable/c/6188cf0c98... WEB
https://git.kernel.org/stable/c/6188cf0c989dea60f2efe800eaebb7d0bd16e2b2
git.kernel.org/stable/c/68619f9653... WEB
https://git.kernel.org/stable/c/68619f965329d2f7b113a3d5811aa23198f39105
git.kernel.org/stable/c/ad805326d8... WEB
https://git.kernel.org/stable/c/ad805326d874062f8bc72a94884f86046148cde3
git.kernel.org/stable/c/b3b76e9f4f... WEB
https://git.kernel.org/stable/c/b3b76e9f4f2476f1135b2ba7743a821db4a0df4b
git.kernel.org/stable/c/b5344e4599... WEB
https://git.kernel.org/stable/c/b5344e459996afb45e30fdc407b41e6674793b21
git.kernel.org/stable/c/d0d82f1214... WEB
https://git.kernel.org/stable/c/d0d82f1214f321143c5dbc2e48e4a4e6c4226895

Frequently Asked Questions

What is CVE-2026-98098?
CVE-2026-98098 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-98098?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98098?
CVE-2026-98098 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98098?
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-vgfp-jj93-v4hf",
  "modified" : "2026-10-03T12:31:27Z",
  "published" : "2026-09-25T12:31:36Z",
  "aliases" : [ "CVE-2026-98098" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: fix NULL deref in tipc_named_node_up() on empty publication list\n\nUser-space applications can bind a large number of service addresses to\none or more sockets. Each binding of a local-scope service address inserts\none entry (publication) into the TIPC name table. If the number of these\npublications exceeds TIPC_MAX_PUBL (65535), protocol service types\n(such as node state and link state) are no longer inserted into the name\ntable. This causes two issues:\n\n1. User-space applications subscribing to node or link up/down events\n   stop receiving notifications.\n\n2. A NULL pointer dereference can occur:\n\n   BUG: kernel NULL pointer dereference, address: 00000000000000d0\n   ...\n   CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc4-default+ #5 PREEMPT(full)\n   ...\n   RIP: 0010:tipc_named_node_up (./include/linux/skbuff.h:2251 net/tipc/name_distr.c:195 net/tipc/name_distr.c:221)\n   ...\n   Call Trace:\n   <IRQ>\n   tipc_node_write_unlock (net/tipc/node.c:428)\n   tipc_rcv (net/tipc/node.c:934 net/tipc/node.c:2189)\n   tipc_udp_recv (net/tipc/udp_media.c:389)\n\n   Thread 1 (tipc_net_finalize) | Thread 2 (named_distribute)\n   -----------------------------|-----------------------------\n                                | ...\n                                | list_for_each_entry(publ, pls, binding_node) {\n                                | ...\n                                | __skb_queue_tail(list, skb);\n                                | ...\n                                | }\n                                | ...\n                                | hdr = buf_msg(skb_peek_tail(list));\n   ...                          |\n   tipc_nametbl_publish();      |\n\n   If 'tipc_nametbl_publish()' (Thread 1) fails because the number of\n   local publications reaches TIPC_MAX_PUBL, list (Thread 2) will be empty. As a\n   result, NULL is passed to 'buf_msg()', leading to a NULL pointer dereference.\n\nFix these issues by allowing protocol service types (node state, link state,\nand topology server) to be inserted into the name table unconditionally.\nThis ensures that users subscribing to these types always receive\nnotifications. In addition, the maximum number of local user publications is\nreduced to (TIPC_MAX_PUBL - 1). This ensures that the maximum bulk size\ncalculated in tipc_link_set_queue_limits() remains valid.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98098"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/246a4b4aace490664927042e93400a6f940d197f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6188cf0c989dea60f2efe800eaebb7d0bd16e2b2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/68619f965329d2f7b113a3d5811aa23198f39105"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ad805326d874062f8bc72a94884f86046148cde3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b3b76e9f4f2476f1135b2ba7743a821db4a0df4b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b5344e459996afb45e30fdc407b41e6674793b21"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d0d82f1214f321143c5dbc2e48e4a4e6c4226895"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:39Z"
  }
}