CVE-2026-98619: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j42x-6wfg-qvw7
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98619
GHSA Identifier GHSA-j42x-6wfg-qvw7
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-98619

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-98619, 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: net: ethtool: keep rtnl_lock for the ioctl self test An offline self test that brings the interface down and back up with netif_close() / netif_open() requires rtnl_lock for both. Since the ethtool IOCTL path became rtnl-optional for ops-locked drivers, the ETHTOOL_TEST ioctl runs holding only the netdev instance lock, so on an ops-locked driver the self test now tears the device down without rtnl_lock. With lockdep this reproduces deterministically on every offline self test on such a driver; note the sole lock held is the instance lock, not rtnl: WARNING: suspicious RCU usage net/core/netpoll.c:207 suspicious rcu_dereference_protected() usage! 1 lock held by ethtool/107: #0: (&dev->lock){+.+.}, at: dev_ethtool Call Trace: netpoll_poll_disable __dev_close_many netif_close_many netif_close fbnic_self_test dev_ethtool_locked dev_ethtool dev_ioctl sock_ioctl __x64_sys_ioctl Without lockdep the same condition trips ASSERT_RTNL() in __dev_close_many() / __dev_open(); that check only samples the global rtnl state, so it can be masked by a concurrent rtnl holder, but the device is still being reconfigured without the lock it requires. The ethtool self_test is a legacy ioctl-only command, so an ETHTOOL_TEST case is only needed on the ioctl path. Add an opt-in bit for drivers whose self test needs rtnl_lock and set it on the ops-locked drivers whose offline self test tears the interface down and up: - fbnic (ops-locked via queue_mgmt_ops): fbnic_self_test() offline path uses netif_close() / netif_open(). - bnxt (ops-locked via queue_mgmt_ops): bnxt_self_test() offline path goes through bnxt_close_nic() / bnxt_half_open_nic() / bnxt_half_close_nic() / bnxt_open_nic(), which close and reopen the device.

References

NVD — CVE-2026-98619 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98619
git.kernel.org/stable/c/1b82958f3f... WEB
https://git.kernel.org/stable/c/1b82958f3f035df5ccaab5430a2302f08a5d5351
git.kernel.org/stable/c/4ca1503491... WEB
https://git.kernel.org/stable/c/4ca1503491f1f25a954c13ac5775bf6775c5abc8

Frequently Asked Questions

What is CVE-2026-98619?
CVE-2026-98619 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-98619?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98619?
CVE-2026-98619 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98619?
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-j42x-6wfg-qvw7",
  "modified" : "2026-10-18T18:31:56Z",
  "published" : "2026-10-18T18:31:56Z",
  "aliases" : [ "CVE-2026-98619" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethtool: keep rtnl_lock for the ioctl self test\n\nAn offline self test that brings the interface down and back up with\nnetif_close() / netif_open() requires rtnl_lock for both. Since the\nethtool IOCTL path became rtnl-optional for ops-locked drivers, the\nETHTOOL_TEST ioctl runs holding only the netdev instance lock, so on an\nops-locked driver the self test now tears the device down without\nrtnl_lock.\n\nWith lockdep this reproduces deterministically on every offline self\ntest on such a driver; note the sole lock held is the instance lock, not\nrtnl:\n\n  WARNING: suspicious RCU usage\n  net/core/netpoll.c:207 suspicious rcu_dereference_protected() usage!\n  1 lock held by ethtool/107:\n   #0: (&dev->lock){+.+.}, at: dev_ethtool\n  Call Trace:\n   netpoll_poll_disable\n   __dev_close_many\n   netif_close_many\n   netif_close\n   fbnic_self_test\n   dev_ethtool_locked\n   dev_ethtool\n   dev_ioctl\n   sock_ioctl\n   __x64_sys_ioctl\n\nWithout lockdep the same condition trips ASSERT_RTNL() in\n__dev_close_many() / __dev_open(); that check only samples the global\nrtnl state, so it can be masked by a concurrent rtnl holder, but the\ndevice is still being reconfigured without the lock it requires.\n\nThe ethtool self_test is a legacy ioctl-only command, so an ETHTOOL_TEST\ncase is only needed on the ioctl path. Add an opt-in bit for drivers whose\nself test needs rtnl_lock and set it on the ops-locked drivers whose\noffline self test tears the interface down and up:\n\n  - fbnic (ops-locked via queue_mgmt_ops): fbnic_self_test() offline path\n    uses netif_close() / netif_open().\n  - bnxt (ops-locked via queue_mgmt_ops): bnxt_self_test() offline path\n    goes through bnxt_close_nic() / bnxt_half_open_nic() /\n    bnxt_half_close_nic() / bnxt_open_nic(), which close and reopen the\n    device.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98619"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1b82958f3f035df5ccaab5430a2302f08a5d5351"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4ca1503491f1f25a954c13ac5775bf6775c5abc8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:14Z"
  }
}