CVE-2026-98737: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-g43c-xvh2-vxh2
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98737
GHSA Identifier GHSA-g43c-xvh2-vxh2
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-98737

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-98737, 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: hci_sync: Fix inquiry cache use-after-free The sync command worker holds hdev->req_lock, but inquiry-cache updates and flushes use hdev->lock. Both hci_acl_create_conn_sync() and hci_stop_discovery_sync() look up entries and read their fields without taking hdev->lock. After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire hdev->lock and flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal. KASAN reported these accesses: BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_acl_create_conn_sync+0x5f1/0x650 hci_cmd_sync_work+0x13c/0x290 Allocated by task 90: hci_inquiry_cache_update+0x3e6/0x7d0 hci_inquiry_result_evt+0x3cb/0x560 Freed by task 93: hci_inquiry_cache_flush+0x111/0x2b0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0 BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_stop_discovery_sync+0x3b1/0x3c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 86: hci_inquiry_cache_update+0x483/0x940 hci_inquiry_result_evt+0x3cb/0x560 Freed by task 91: hci_inquiry_cache_flush+0x13e/0x2f0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0 Hold hdev->lock across each lookup and all reads from its result. Copy the remote address before unlocking so discovery cancellation does not retain a cache entry pointer. Release the lock before sending synchronous HCI commands, since their completion handlers may need the same lock.

References

NVD — CVE-2026-98737 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98737
git.kernel.org/stable/c/333257e6e4... WEB
https://git.kernel.org/stable/c/333257e6e4a7bcaaea82fd357121d0f1e6b76c7b
git.kernel.org/stable/c/52edf1c0e5... WEB
https://git.kernel.org/stable/c/52edf1c0e59dea37b8368c4a2559dca96b2fdfea
git.kernel.org/stable/c/8ed67535fd... WEB
https://git.kernel.org/stable/c/8ed67535fdff40ca652bcd4ac7da68d11d01bd34
git.kernel.org/stable/c/a642f498f0... WEB
https://git.kernel.org/stable/c/a642f498f0b08f2aa9f4a69468db92f57a72349d

Frequently Asked Questions

What is CVE-2026-98737?
CVE-2026-98737 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-98737?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98737?
CVE-2026-98737 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98737?
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-g43c-xvh2-vxh2",
  "modified" : "2026-10-18T18:32:01Z",
  "published" : "2026-10-18T18:32:01Z",
  "aliases" : [ "CVE-2026-98737" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: Fix inquiry cache use-after-free\n\nThe sync command worker holds hdev->req_lock, but inquiry-cache updates\nand flushes use hdev->lock. Both hci_acl_create_conn_sync() and\nhci_stop_discovery_sync() look up entries and read their fields without\ntaking hdev->lock.\n\nAfter either lookup returns, a concurrent HCIINQUIRY ioctl can acquire\nhdev->lock and flush the cache, freeing the entry. The worker then reads\nthe freed entry while preparing a create-connection or remote-name-cancel\ncommand. The list traversal also races with cache updates and removal.\n\nKASAN reported these accesses:\n\n  BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650\n  Workqueue: hci0 hci_cmd_sync_work\n  Call Trace:\n   hci_acl_create_conn_sync+0x5f1/0x650\n   hci_cmd_sync_work+0x13c/0x290\n\n  Allocated by task 90:\n   hci_inquiry_cache_update+0x3e6/0x7d0\n   hci_inquiry_result_evt+0x3cb/0x560\n\n  Freed by task 93:\n   hci_inquiry_cache_flush+0x111/0x2b0\n   hci_inquiry+0x2f2/0x780\n   hci_sock_ioctl+0x269/0x5f0\n\n  BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0\n  Workqueue: hci0 hci_cmd_sync_work\n  Call Trace:\n   hci_stop_discovery_sync+0x3b1/0x3c0\n   hci_cmd_sync_work+0x173/0x300\n\n  Allocated by task 86:\n   hci_inquiry_cache_update+0x483/0x940\n   hci_inquiry_result_evt+0x3cb/0x560\n\n  Freed by task 91:\n   hci_inquiry_cache_flush+0x13e/0x2f0\n   hci_inquiry+0x2f2/0x780\n   hci_sock_ioctl+0x269/0x5f0\n\nHold hdev->lock across each lookup and all reads from its result. Copy the\nremote address before unlocking so discovery cancellation does not retain\na cache entry pointer. Release the lock before sending synchronous HCI\ncommands, since their completion handlers may need the same lock.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98737"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/333257e6e4a7bcaaea82fd357121d0f1e6b76c7b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/52edf1c0e59dea37b8368c4a2559dca96b2fdfea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8ed67535fdff40ca652bcd4ac7da68d11d01bd34"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a642f498f0b08f2aa9f4a69468db92f57a72349d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:27Z"
  }
}