CVE-2026-98601: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98601 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-98601 at a Glance
How to Fix CVE-2026-98601
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-98601, 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-98601?
Which Software versions are affected?
What version fixes CVE-2026-98601?
What CWE is associated with CVE-2026-98601?
How can I check Maven dependencies for CVE-2026-98601?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f3q9-4q8h-j7xp",
"modified" : "2026-10-18T18:31:56Z",
"published" : "2026-10-18T18:31:56Z",
"aliases" : [ "CVE-2026-98601" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btintel_pcie: validate device-supplied DMA indices\n\nIn btintel_pcie_msix_rx_handle(), the driver processes RX completion\ndescriptors (urbd1) written by the PCIe device into DMA-coherent memory.\nurbd1->frbd_tag (a 16-bit field fully controlled by the device firmware\nvia DMA) is used directly as an array index into rxq->bufs[] without any\nbounds check. rxq->bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)\nentries, while frbd_tag can be any value 0-65535. A malicious or\nmalfunctioning device can write an out-of-range frbd_tag, causing the\ndriver to dereference an out-of-bounds data_buf pointer.\n\nAdditionally, cr_hia is read from a DMA-shared index array also writable\nby the device; if the device sets cr_hia >= rxq->count, the while-loop\nnever terminates because cr_tia is wrapped via modulo rxq->count and can\nnever equal an out-of-range cr_hia.\n\nAdd bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia\nin the TX path. Log invalid values with bt_dev_err before returning.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98601"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/37a11129345337efd6eef8e62b03b6348cd0dd8b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/8ec5838a35b03ac0cf3602452a369898051ffaf9"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b29b70bfa12133423924fcd0327c19a802f7e368"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f42cd95e679d5b78611cd2208cd1c41ad0045ffa"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:12Z"
}
}