CVE-2026-98739: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-jg2j-fxrh-w676
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98739
GHSA Identifier GHSA-jg2j-fxrh-w676
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-98739

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-98739, 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: Bluetooth: RFCOMM: Fix initial port reference race For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference. The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible: 1. Install and release each obtain a reference with rfcomm_dev_get(). 2. Release observes RFCOMM_TTY_OWNED clear. 3. Install sets RFCOMM_TTY_OWNED and drops the initial reference. 4. Release drops the same initial reference again. 5. TTY cleanup drops its reference and frees the device. 6. Release performs its final tty_port_put() on the freed port. KASAN reported: BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190 Write of size 4 at addr ffff8881001d3d5c by task poc/92 Call Trace: tty_port_put+0x22/0x190 rfcomm_dev_ioctl+0x1d4/0x1930 sock_do_ioctl+0x110/0x260 sock_ioctl+0x380/0x590 __x64_sys_ioctl+0x134/0x1c0 Allocated by task 88: rfcomm_dev_ioctl+0x8f6/0x1930 sock_do_ioctl+0x110/0x260 sock_ioctl+0x380/0x590 __x64_sys_ioctl+0x134/0x1c0 Freed by task 65: kfree+0x131/0x3c0 rfcomm_dev_destruct+0x23b/0x2f0 release_one_tty+0xc1/0x370 process_one_work+0x661/0x1090 Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.

References

NVD — CVE-2026-98739 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98739
git.kernel.org/stable/c/0a554901bd... WEB
https://git.kernel.org/stable/c/0a554901bd227537f79220443b2b36d585d62893
git.kernel.org/stable/c/2d696c1ed3... WEB
https://git.kernel.org/stable/c/2d696c1ed3468dcb62578a3911e687110d463520
git.kernel.org/stable/c/a03ccf1ab7... WEB
https://git.kernel.org/stable/c/a03ccf1ab77380d4c4a3c56552e12de4a83efa21
git.kernel.org/stable/c/e5aa7fbf7a... WEB
https://git.kernel.org/stable/c/e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b

Frequently Asked Questions

What is CVE-2026-98739?
CVE-2026-98739 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-98739?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98739?
CVE-2026-98739 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98739?
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-jg2j-fxrh-w676",
  "modified" : "2026-10-18T18:32:01Z",
  "published" : "2026-10-18T18:32:01Z",
  "aliases" : [ "CVE-2026-98739" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: Fix initial port reference race\n\nFor RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and\n__rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the\ninitial tty_port reference. The release path tests the bit separately\nfrom the install path setting it, so both can drop that reference.\n\nThe synchronous hangup does not prevent this race: port->tty is not\nassigned until tty_port_open(), after installation. The following\ninterleaving is possible:\n\n  1. Install and release each obtain a reference with rfcomm_dev_get().\n  2. Release observes RFCOMM_TTY_OWNED clear.\n  3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.\n  4. Release drops the same initial reference again.\n  5. TTY cleanup drops its reference and frees the device.\n  6. Release performs its final tty_port_put() on the freed port.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190\n  Write of size 4 at addr ffff8881001d3d5c by task poc/92\n\n  Call Trace:\n   tty_port_put+0x22/0x190\n   rfcomm_dev_ioctl+0x1d4/0x1930\n   sock_do_ioctl+0x110/0x260\n   sock_ioctl+0x380/0x590\n   __x64_sys_ioctl+0x134/0x1c0\n\n  Allocated by task 88:\n   rfcomm_dev_ioctl+0x8f6/0x1930\n   sock_do_ioctl+0x110/0x260\n   sock_ioctl+0x380/0x590\n   __x64_sys_ioctl+0x134/0x1c0\n\n  Freed by task 65:\n   kfree+0x131/0x3c0\n   rfcomm_dev_destruct+0x23b/0x2f0\n   release_one_tty+0xc1/0x370\n   process_one_work+0x661/0x1090\n\nUse test_and_set_bit() in both paths so that only the caller that changes\nRFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path\nkeeps its own lookup reference until release or TTY cleanup, preserving\nthe existing callback ordering and error handling.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98739"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0a554901bd227537f79220443b2b36d585d62893"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2d696c1ed3468dcb62578a3911e687110d463520"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a03ccf1ab77380d4c4a3c56552e12de4a83efa21"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e5aa7fbf7a4446bb89f0b8394b2dfc1a6b6aba5b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:27Z"
  }
}