CVE-2026-98688: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-g38j-2fmx-j974
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98688
GHSA Identifier GHSA-g38j-2fmx-j974
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-98688

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-98688, 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: thunderbolt: Fix NULL dereference in tb_remove_work() There is a slight race between tb_remove_work() and tb_domain_remove() which leads to dereferencing a NULL tb->root_switch pointer inside tb_free_unplugged_xdomains(): Thread A Thread B tb_remove_work() tb_domain_remove() mutex_lock(&tb->lock) tb_stop() /* doesn't cancel a running callback */ cancel_delayed_work(&tcm->remove_work) ... tb_switch_remove(tb->root_switch) tb->root_switch = NULL mutex_unlock(&tb->lock) mutex_lock(&tb->lock) ... /* without checking ->root_switch */ tb_free_unplugged_xdomains(tb->root_switch) mutex_unlock(&tb->lock) Commit a8937f35cf39 ("thunderbolt: Remove XDomain from the bus without holding tb->lock") doesn't seem right to move tb_free_unplugged_xdomains() out of the &tb->lock section and the check for tb->root_switch, in particular. It states: For this reason separate removing the XDomain from the topology data structures (where we need the lock) from unregistering the device from the bus (where remove callbacks of the drivers are being called). tb_free_unplugged_xdomains() belongs to the former group of functions requiring the lock. And it also calls tb_xdomain_remove() which should only be called with &tb->lock held. Found by Linux Verification Center (linuxtesting.org) with Svace static analysis tool.

References

NVD — CVE-2026-98688 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98688
git.kernel.org/stable/c/2f4cd43faa... WEB
https://git.kernel.org/stable/c/2f4cd43faa9d6470b30a9fbcbac6584db8108c1f
git.kernel.org/stable/c/4310c6b8e7... WEB
https://git.kernel.org/stable/c/4310c6b8e75d6a47f7548e5948fbe6318aa4440a

Frequently Asked Questions

What is CVE-2026-98688?
CVE-2026-98688 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-98688?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98688?
CVE-2026-98688 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98688?
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-g38j-2fmx-j974",
  "modified" : "2026-10-18T18:31:59Z",
  "published" : "2026-10-18T18:31:59Z",
  "aliases" : [ "CVE-2026-98688" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nthunderbolt: Fix NULL dereference in tb_remove_work()\n\nThere is a slight race between tb_remove_work() and tb_domain_remove()\nwhich leads to dereferencing a NULL tb->root_switch pointer inside\ntb_free_unplugged_xdomains():\n\n        Thread A                            Thread B\n\n  tb_remove_work()\n                                    tb_domain_remove()\n                                      mutex_lock(&tb->lock)\n                                      tb_stop()\n                                        /* doesn't cancel a running callback */\n                                        cancel_delayed_work(&tcm->remove_work)\n                                        ...\n                                        tb_switch_remove(tb->root_switch)\n                                        tb->root_switch = NULL\n                                      mutex_unlock(&tb->lock)\n    mutex_lock(&tb->lock)\n    ...\n    /* without checking ->root_switch */\n    tb_free_unplugged_xdomains(tb->root_switch)\n    mutex_unlock(&tb->lock)\n\nCommit a8937f35cf39 (\"thunderbolt: Remove XDomain from the bus without\nholding tb->lock\") doesn't seem right to move tb_free_unplugged_xdomains()\nout of the &tb->lock section and the check for tb->root_switch, in\nparticular.  It states:\n\n  For this reason separate removing the XDomain from the topology data\n  structures (where we need the lock) from unregistering the device from\n  the bus (where remove callbacks of the drivers are being called).\n\ntb_free_unplugged_xdomains() belongs to the former group of functions\nrequiring the lock.  And it also calls tb_xdomain_remove() which should\nonly be called with &tb->lock held.\n\nFound by Linux Verification Center (linuxtesting.org) with Svace static\nanalysis tool.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98688"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2f4cd43faa9d6470b30a9fbcbac6584db8108c1f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4310c6b8e75d6a47f7548e5948fbe6318aa4440a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:22Z"
  }
}