CVE-2026-98752: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98752 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-98752 at a Glance
How to Fix CVE-2026-98752
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.
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-98752, 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
References
Frequently Asked Questions
What is CVE-2026-98752?
Which Software versions are affected?
What version fixes CVE-2026-98752?
What CWE is associated with CVE-2026-98752?
How can I check Maven dependencies for CVE-2026-98752?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2697-8gj7-2gh6",
"modified" : "2026-10-18T18:32:02Z",
"published" : "2026-10-18T18:32:02Z",
"aliases" : [ "CVE-2026-98752" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntty: port: fix tty_port_tty_vhangup() race\n\nDrivers rely on tty_port_tty_vhangup() to synchronously hang up their\nports before tearing down resources as part of deregistration (e.g. on\nphysical disconnect).\n\nIf tty_port_tty_vhangup() races with another hangup it may however\nreturn before the port has been shut down. This is in turn can lead to\nuse-after-free and NULL-pointer dereferences in racing ioctls (including\na synchronous hangup) and in processing of racing asynchronous hangups\n(carrier loss).\n\nAdd the missing serialisation to tty_port_tty_vhangup() and\ntty_port_hangup() so that the former does not return until the port has\nbeen shut down also when there is a racing hangup.\n\nNote that serial core does not use tty_port_hangup(), but it already\nholds the port mutex when clearing port->tty and shutting down the port\nin uart_hangup().",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98752"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/017b18addbe8dcace1a569a00d40ed1ba1e03f4c"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6b7be3b9b857947e9c1338d4919d4ebd3b75e907"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6d1a984afc3ca477dab3e51ec806671d443ad524"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b48820de8c1a596c5b99775524dfce73c6576c5d"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:28Z"
}
}