CVE-2026-89973: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-9393-xpw8-3983
Share
CVSS 8.2
Published
Advisory Summary

CVE-2026-89973 is a HIGH (CVSS 8.2) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89973 at a Glance

CVE Identifier CVE-2026-89973
GHSA Identifier GHSA-9393-xpw8-3983
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-89973

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-89973, 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: nvme-tcp: check the data direction of a C2HData PDU nvme_tcp_handle_c2h_data() finds the request by command id and checks that it has a payload, but it does not check that the command asked for data to be read. A controller that answers a write command with C2HData therefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits WARN_ON_ONCE(i->data_source) and returns 0. The receive path turns that into -EFAULT and resets the controller. No data is copied, so this is not memory corruption. What a controller gets is a kernel warning it can raise at will, which is fatal on a host booted with panic_on_warn. The send path already knows the direction - it consults rq_data_dir() when it builds a command - and nvme_tcp_handle_r2t() checks the length and the offset of the request it names. The C2HData path does not check the direction at all. Reject a C2HData PDU whose command is not a read. Rejecting it fails the command and resets the controller, as the neighbouring check in this function does; what goes away is the warning. [ 6.885580] ------------[ cut here ]------------ [ 6.886457] WARNING: lib/iov_iter.c:193 at _copy_to_iter+0x289/0x1330, CPU#0: kworker/0:1H/71 [ 6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy) [ 6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work [ 6.891875] RIP: 0010:_copy_to_iter+0x289/0x1330 [ 6.903739] Call Trace: [ 6.904085] <TASK> [ 6.909254] __skb_datagram_iter+0x433/0x820 [ 6.911026] skb_copy_datagram_iter+0x37/0x120 [ 6.911622] nvme_tcp_recv_skb+0xa07/0x4320 [ 6.913378] __tcp_read_sock+0x1ab/0x810 [ 6.915788] nvme_tcp_try_recv+0x152/0x1e0 [ 6.918222] nvme_tcp_io_work+0x1e4/0x6c0 [ 6.926906] </TASK> [ 6.927226] ---[ end trace 0000000000000000 ]--- [ 6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data [ 6.928709] nvme nvme0: receive failed: -14

References

NVD — CVE-2026-89973 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89973
git.kernel.org/stable/c/0673a2affe... WEB
https://git.kernel.org/stable/c/0673a2affe45ca76b60de31a83c67b1e60f81bde
git.kernel.org/stable/c/5b115d932f... WEB
https://git.kernel.org/stable/c/5b115d932f6e769ac80783fb18edd21b0aed256e
git.kernel.org/stable/c/80d56202fb... WEB
https://git.kernel.org/stable/c/80d56202fbdff8906be6954b2776e5c14a4026f2
git.kernel.org/stable/c/980d990f3c... WEB
https://git.kernel.org/stable/c/980d990f3c0560d7dfbfbf14699651fdf02f26ee
git.kernel.org/stable/c/a0c389b8a4... WEB
https://git.kernel.org/stable/c/a0c389b8a495bda1eb719d2503853c924b7a8355
git.kernel.org/stable/c/b4af7999a9... WEB
https://git.kernel.org/stable/c/b4af7999a998787d5eb6facb5a333e04a4f1d2d9
git.kernel.org/stable/c/df74950ba6... WEB
https://git.kernel.org/stable/c/df74950ba6008655d4a977d17df7faf4b6e52b74
git.kernel.org/stable/c/f83af377c1... WEB
https://git.kernel.org/stable/c/f83af377c148f6ad94b41c0e8313f12adf45e1c1

Frequently Asked Questions

What is CVE-2026-89973?
CVE-2026-89973 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-89973?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-89973?
CVE-2026-89973 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H.
What CWE is associated with CVE-2026-89973?
CVE-2026-89973 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89973?
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-9393-xpw8-3983",
  "modified" : "2026-09-16T15:31:03Z",
  "published" : "2026-09-16T12:30:44Z",
  "aliases" : [ "CVE-2026-89973" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: check the data direction of a C2HData PDU\n\nnvme_tcp_handle_c2h_data() finds the request by command id and checks\nthat it has a payload, but it does not check that the command asked for\ndata to be read.  A controller that answers a write command with C2HData\ntherefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits\nWARN_ON_ONCE(i->data_source) and returns 0.  The receive path turns that\ninto -EFAULT and resets the controller.\n\nNo data is copied, so this is not memory corruption.  What a controller\ngets is a kernel warning it can raise at will, which is fatal on a host\nbooted with panic_on_warn.\n\nThe send path already knows the direction - it consults rq_data_dir()\nwhen it builds a command - and nvme_tcp_handle_r2t() checks the length\nand the offset of the request it names.  The C2HData path does not check\nthe direction at all.\n\nReject a C2HData PDU whose command is not a read.  Rejecting it fails\nthe command and resets the controller, as the neighbouring check in this\nfunction does; what goes away is the warning.\n\n  [    6.885580] ------------[ cut here ]------------\n  [    6.886457] WARNING: lib/iov_iter.c:193 at _copy_to_iter+0x289/0x1330, CPU#0: kworker/0:1H/71\n  [    6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy)\n  [    6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work\n  [    6.891875] RIP: 0010:_copy_to_iter+0x289/0x1330\n  [    6.903739] Call Trace:\n  [    6.904085]  <TASK>\n  [    6.909254]  __skb_datagram_iter+0x433/0x820\n  [    6.911026]  skb_copy_datagram_iter+0x37/0x120\n  [    6.911622]  nvme_tcp_recv_skb+0xa07/0x4320\n  [    6.913378]  __tcp_read_sock+0x1ab/0x810\n  [    6.915788]  nvme_tcp_try_recv+0x152/0x1e0\n  [    6.918222]  nvme_tcp_io_work+0x1e4/0x6c0\n  [    6.926906]  </TASK>\n  [    6.927226] ---[ end trace 0000000000000000 ]---\n  [    6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data\n  [    6.928709] nvme nvme0: receive failed:  -14",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89973"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0673a2affe45ca76b60de31a83c67b1e60f81bde"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5b115d932f6e769ac80783fb18edd21b0aed256e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/80d56202fbdff8906be6954b2776e5c14a4026f2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/980d990f3c0560d7dfbfbf14699651fdf02f26ee"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a0c389b8a495bda1eb719d2503853c924b7a8355"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b4af7999a998787d5eb6facb5a333e04a4f1d2d9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/df74950ba6008655d4a977d17df7faf4b6e52b74"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f83af377c148f6ad94b41c0e8313f12adf45e1c1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:08Z"
  }
}