CVE-2026-98734: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4q25-9c2v-7w4q
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98734
GHSA Identifier GHSA-4q25-9c2v-7w4q
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-98734

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-98734, 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_core: Serialize SCO and ISO scheduling with teardown hci_low_sent() selects a connection under RCU but drops the read lock before calculating its quota and returning it to the scheduler. The connection is then used without lifetime protection by hci_sched_iso() and hci_sched_sco(). After the TX worker drops the RCU read lock, hci_abort_conn_sync() on hdev->req_workqueue can remove the connection from the hash, complete synchronize_rcu(), purge its queues and release it. The TX worker on hdev->workqueue can then access the freed connection in hci_quote_sent() or while dequeuing packets and updating conn->sent. KASAN reported: BUG: KASAN: slab-use-after-free in hci_low_sent+0x730/0x840 Workqueue: hci0 hci_tx_work Call Trace: hci_low_sent+0x730/0x840 hci_sched_iso+0x25e/0x4d0 hci_tx_work+0x239/0xcb0 Allocated by task 93: __hci_conn_add+0x16f/0x1b40 hci_bind_bis+0x782/0x17b0 hci_connect_bis+0xa0/0x510 iso_sock_connect+0x589/0x1050 Freed by task 88: kfree+0x131/0x3c0 device_release+0xc8/0x240 kobject_put+0x14d/0x280 hci_conn_del+0x55a/0xe80 hci_disconnect_sync+0x156/0x180 hci_abort_conn_sync+0x3e7/0x940 hci_cmd_sync_work+0x13c/0x290 Hold hci_dev_lock() across connection selection and transmission in both SCO and ISO scheduling, serializing them with connection teardown. This also prevents queuing completion timestamps after the connection queues have been purged. Extending RCU across transmission would be unsafe because the transmit path can sleep. Keep the ISO timeout check outside the mutex since hci_link_tx_to() takes it itself. The preceding channel fix already holds this mutex in the ACL and LE schedulers, which call the SCO scheduler between packets. Move the SCO body to __hci_sched_sco(), assert that its caller holds the mutex, and use it directly from these locked paths. Keep a locking hci_sched_sco() wrapper for the direct calls from hci_tx_work(). This avoids recursively acquiring the device mutex while preserving the scheduling order. Remove the obsolete claim that connection removal disables TX.

References

NVD — CVE-2026-98734 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98734
git.kernel.org/stable/c/101825c09a... WEB
https://git.kernel.org/stable/c/101825c09ad6b7daa6cf4c9e6b1720b13de15596
git.kernel.org/stable/c/1681f97afd... WEB
https://git.kernel.org/stable/c/1681f97afdf92e8557f2f3118ddc898471b5d299
git.kernel.org/stable/c/848a7a91c7... WEB
https://git.kernel.org/stable/c/848a7a91c7f03675d3bd8db6f7721cbf9cb50e21
git.kernel.org/stable/c/ecdb1c66d8... WEB
https://git.kernel.org/stable/c/ecdb1c66d8e14e63731c52d6fbcfa604064913c4

Frequently Asked Questions

What is CVE-2026-98734?
CVE-2026-98734 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-98734?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98734?
CVE-2026-98734 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98734?
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-4q25-9c2v-7w4q",
  "modified" : "2026-10-18T18:32:01Z",
  "published" : "2026-10-18T18:32:01Z",
  "aliases" : [ "CVE-2026-98734" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Serialize SCO and ISO scheduling with teardown\n\nhci_low_sent() selects a connection under RCU but drops the read lock\nbefore calculating its quota and returning it to the scheduler. The\nconnection is then used without lifetime protection by hci_sched_iso()\nand hci_sched_sco().\n\nAfter the TX worker drops the RCU read lock, hci_abort_conn_sync() on\nhdev->req_workqueue can remove the connection from the hash, complete\nsynchronize_rcu(), purge its queues and release it. The TX worker on\nhdev->workqueue can then access the freed connection in hci_quote_sent()\nor while dequeuing packets and updating conn->sent.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in hci_low_sent+0x730/0x840\n  Workqueue: hci0 hci_tx_work\n  Call Trace:\n   hci_low_sent+0x730/0x840\n   hci_sched_iso+0x25e/0x4d0\n   hci_tx_work+0x239/0xcb0\n\n  Allocated by task 93:\n   __hci_conn_add+0x16f/0x1b40\n   hci_bind_bis+0x782/0x17b0\n   hci_connect_bis+0xa0/0x510\n   iso_sock_connect+0x589/0x1050\n\n  Freed by task 88:\n   kfree+0x131/0x3c0\n   device_release+0xc8/0x240\n   kobject_put+0x14d/0x280\n   hci_conn_del+0x55a/0xe80\n   hci_disconnect_sync+0x156/0x180\n   hci_abort_conn_sync+0x3e7/0x940\n   hci_cmd_sync_work+0x13c/0x290\n\nHold hci_dev_lock() across connection selection and transmission in both\nSCO and ISO scheduling, serializing them with connection teardown. This\nalso prevents queuing completion timestamps after the connection queues\nhave been purged. Extending RCU across transmission would be unsafe\nbecause the transmit path can sleep. Keep the ISO timeout check outside\nthe mutex since hci_link_tx_to() takes it itself.\n\nThe preceding channel fix already holds this mutex in the ACL and LE\nschedulers, which call the SCO scheduler between packets. Move the SCO\nbody to __hci_sched_sco(), assert that its caller holds the mutex, and\nuse it directly from these locked paths. Keep a locking hci_sched_sco()\nwrapper for the direct calls from hci_tx_work(). This avoids recursively\nacquiring the device mutex while preserving the scheduling order.\n\nRemove the obsolete claim that connection removal disables TX.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98734"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/101825c09ad6b7daa6cf4c9e6b1720b13de15596"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1681f97afdf92e8557f2f3118ddc898471b5d299"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/848a7a91c7f03675d3bd8db6f7721cbf9cb50e21"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ecdb1c66d8e14e63731c52d6fbcfa604064913c4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:27Z"
  }
}