CVE-2026-98738: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-pp83-8gx8-qvjg
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98738
GHSA Identifier GHSA-pp83-8gx8-qvjg
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-98738

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-98738, 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: Serialize SMP remote OOB data access build_pairing_cmd() looks up remote OOB data and copies its contents without holding hdev->lock, which serializes the list's writers. After SMP finds an entry, a concurrent management Remove Remote OOB Data command can unlink and free it before SMP reads its present flag or copies its random and confirmation values. Removal can also invalidate an entry while the lookup is still traversing the list. KASAN reported: BUG: KASAN: slab-use-after-free in build_pairing_cmd+0x948/0x9b0 Call Trace: build_pairing_cmd+0x948/0x9b0 smp_recv_cb+0x459f/0x8110 l2cap_recv_frame+0xf14/0x9190 l2cap_recv_acldata+0xa64/0xd40 hci_rx_work+0x4ca/0x730 Allocated by task 87: hci_add_remote_oob_data+0x11d/0x530 add_remote_oob_data+0x282/0x400 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 93: hci_remote_oob_data_clear+0x108/0x1c0 remove_remote_oob_data+0x198/0x220 hci_sock_sendmsg+0x1033/0x1ea0 Taking hdev->lock in build_pairing_cmd() would recurse for callers that already hold it and invert the device-to-L2CAP lock order on the receive path. Add a per-device remote_oob_lock instead, held across the SMP lookup and copies and by the add, remove and clear helpers. Cover initialization and in-place updates as well, so SMP cannot read partially initialized or updated OOB values. Release the mutex on allocation failure, preserving the existing error return. The new critical sections acquire no device, connection or channel locks. Writers retain their existing hdev->lock protection, which continues to serialize the other readers without changing their locking or behavior.

References

NVD — CVE-2026-98738 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98738
git.kernel.org/stable/c/1e11412a1b... WEB
https://git.kernel.org/stable/c/1e11412a1b9854a89d044576d616675b16141d87
git.kernel.org/stable/c/81a2345f19... WEB
https://git.kernel.org/stable/c/81a2345f1984f0b36d3226571bc196316a01b648
git.kernel.org/stable/c/889c61e3d0... WEB
https://git.kernel.org/stable/c/889c61e3d0f1091a958e4b2a24b20bab23d915c4
git.kernel.org/stable/c/df5162eeb1... WEB
https://git.kernel.org/stable/c/df5162eeb10e69fe0c2349503882c4a09077f001

Frequently Asked Questions

What is CVE-2026-98738?
CVE-2026-98738 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-98738?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98738?
CVE-2026-98738 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98738?
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-pp83-8gx8-qvjg",
  "modified" : "2026-10-18T18:32:01Z",
  "published" : "2026-10-18T18:32:01Z",
  "aliases" : [ "CVE-2026-98738" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Serialize SMP remote OOB data access\n\nbuild_pairing_cmd() looks up remote OOB data and copies its contents\nwithout holding hdev->lock, which serializes the list's writers. After\nSMP finds an entry, a concurrent management Remove Remote OOB Data\ncommand can unlink and free it before SMP reads its present flag or\ncopies its random and confirmation values. Removal can also invalidate\nan entry while the lookup is still traversing the list.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in build_pairing_cmd+0x948/0x9b0\n  Call Trace:\n   build_pairing_cmd+0x948/0x9b0\n   smp_recv_cb+0x459f/0x8110\n   l2cap_recv_frame+0xf14/0x9190\n   l2cap_recv_acldata+0xa64/0xd40\n   hci_rx_work+0x4ca/0x730\n\n  Allocated by task 87:\n   hci_add_remote_oob_data+0x11d/0x530\n   add_remote_oob_data+0x282/0x400\n   hci_sock_sendmsg+0x1033/0x1ea0\n\n  Freed by task 93:\n   hci_remote_oob_data_clear+0x108/0x1c0\n   remove_remote_oob_data+0x198/0x220\n   hci_sock_sendmsg+0x1033/0x1ea0\n\nTaking hdev->lock in build_pairing_cmd() would recurse for callers that\nalready hold it and invert the device-to-L2CAP lock order on the receive\npath. Add a per-device remote_oob_lock instead, held across the SMP\nlookup and copies and by the add, remove and clear helpers. Cover\ninitialization and in-place updates as well, so SMP cannot read partially\ninitialized or updated OOB values. Release the mutex on allocation\nfailure, preserving the existing error return.\n\nThe new critical sections acquire no device, connection or channel locks.\nWriters retain their existing hdev->lock protection, which continues to\nserialize the other readers without changing their locking or behavior.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98738"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1e11412a1b9854a89d044576d616675b16141d87"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/81a2345f1984f0b36d3226571bc196316a01b648"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/889c61e3d0f1091a958e4b2a24b20bab23d915c4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/df5162eeb10e69fe0c2349503882c4a09077f001"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:27Z"
  }
}