CVE-2026-98617: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j327-5j79-p464
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98617
GHSA Identifier GHSA-j327-5j79-p464
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-98617

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-98617, 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: eth: fbnic: use the Rx queue napi pointer to find the napi vector The queue management ndos pick the napi vector for an Rx queue with: nv = fbn->napi[idx % fbn->num_napi]; The issue is this is only correct in the cases where there are no standalone Tx vectors. In those cases we were allocating the Tx vectors first and then the Rx so the queues would be pointing to Tx NAPI vectors instead of the Rx ones. The mapping the ndos want is already recorded. fbnic_set_netif_napi() publishes it with netif_queue_set_napi(), which stores the napi pointer in netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again. Both run under the netdev instance lock that the queue management ndos also hold, so the pointer can be read directly. Use it and drop the divide. The pointer is NULL exactly while the datapath is down, so fbnic_queue_mem_alloc() can reject that case rather than reaching into freed state: netdev_rx_queue_restart() calls it before it tests netif_running(), and fbnic_pm_suspend() leaves netif_running() true across a PCIe recovery that never completes, so a queue restart can arrive after fbnic_stop() has freed the rings and the vectors. fbnic_stop() clears the association in fbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the NULL is always published first. fbnic_queue_start() and fbnic_queue_stop() need no check of their own, as netdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc() has succeeded under the same instance lock.

References

NVD — CVE-2026-98617 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98617
git.kernel.org/stable/c/1fb569cf3b... WEB
https://git.kernel.org/stable/c/1fb569cf3bf97e552f465b2c719e36b48ae7c18b
git.kernel.org/stable/c/b5d9e9d4d0... WEB
https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e

Frequently Asked Questions

What is CVE-2026-98617?
CVE-2026-98617 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-98617?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98617?
CVE-2026-98617 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98617?
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-j327-5j79-p464",
  "modified" : "2026-10-18T18:31:56Z",
  "published" : "2026-10-18T18:31:56Z",
  "aliases" : [ "CVE-2026-98617" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\neth: fbnic: use the Rx queue napi pointer to find the napi vector\n\nThe queue management ndos pick the napi vector for an Rx queue with:\n\tnv = fbn->napi[idx % fbn->num_napi];\n\nThe issue is this is only correct in the cases where there are no\nstandalone Tx vectors. In those cases we were allocating the Tx vectors\nfirst and then the Rx so the queues would be pointing to Tx NAPI vectors\ninstead of the Rx ones.\n\nThe mapping the ndos want is already recorded.  fbnic_set_netif_napi()\npublishes it with netif_queue_set_napi(), which stores the napi pointer\nin netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again.\nBoth run under the netdev instance lock that the queue management ndos\nalso hold, so the pointer can be read directly.\n\nUse it and drop the divide.  The pointer is NULL exactly while the\ndatapath is down, so fbnic_queue_mem_alloc() can reject that case rather\nthan reaching into freed state: netdev_rx_queue_restart() calls it\nbefore it tests netif_running(), and fbnic_pm_suspend() leaves\nnetif_running() true across a PCIe recovery that never completes, so a\nqueue restart can arrive after fbnic_stop() has freed the rings and the\nvectors.  fbnic_stop() clears the association in\nfbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the\nNULL is always published first.  fbnic_queue_start() and\nfbnic_queue_stop() need no check of their own, as\nnetdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc()\nhas succeeded under the same instance lock.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98617"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1fb569cf3bf97e552f465b2c719e36b48ae7c18b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:14Z"
  }
}