CVE-2026-89974: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6hqx-63gq-9x2p
CVSS 7.5
Published
Advisory Summary

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

CVE-2026-89974 at a Glance

CVE Identifier CVE-2026-89974
GHSA Identifier GHSA-6hqx-63gq-9x2p
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

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

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

How to Fix CVE-2026-89974

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-89974, 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-fc: fix double free of fabrics options when nvme_add_ctrl() fails nvmf_create_ctrl() owns the fabrics options and frees them whenever ->create_ctrl() returns an error, so a transport must not free them on its own error paths. nvme-fc tracks this by testing ctrl->ctrl.opts in nvme_fc_ctrl_free(), which requires nvme_fc_init_ctrl() to clear that pointer on every error exit. The coupling is implicit, and commit 1a9e218195a5 ("nvme: split device add from initialization") broke it by adding a second error exit. When nvme_add_ctrl() fails, nvme_fc_init_ctrl() jumps to out_put_ctrl:, past the "ctrl->ctrl.opts = NULL" that only sits on the fail_ctrl: path, so nvme_fc_ctrl_free() frees the options and nvmf_create_ctrl() frees them a second time: BUG: KASAN: slab-use-after-free in nvmf_free_options+0x30/0x190 nvmf_free_options+0x30/0x190 drivers/nvme/host/fabrics.c:1284 nvmf_create_ctrl drivers/nvme/host/fabrics.c:1374 [inline] Freed by task 5534: nvme_fc_ctrl_free drivers/nvme/host/fc.c:2374 [inline] nvme_fc_init_ctrl+0xe17/0x1450 drivers/nvme/host/fc.c:3605 nvme_add_ctrl() fails when dev_set_name() cannot allocate, so this is reachable under memory pressure or fault injection. Without KASAN the options are freed twice. Rather than clear the pointer on the second exit as well, derive ownership the way nvme-tcp, nvme-rdma and nvme-loop do, from list membership: their free_ctrl leaves the options alone unless the controller made it onto the transport list. The list cannot simply be populated on the success path as it is there. nvme-fc runs the initial connect synchronously via flush_delayed_work(), and the controller has to be reachable on rport->ctrl_list for the whole of it: nvme_fc_unregister_remoteport() needs to find it to signal connectivity loss, nvme_fc_match_disconn_ls() matches an incoming Disconnect Association LS against ctrl->association_id, which is only assigned during that window, nvme_fc_resume_controller() needs it on remoteport re-registration, and nvme_fc_existing_controller() uses it to reject a duplicate connect racing the one in flight. Keep the insertion where it is and add a fail_unlist: label, falling into fail_ctrl:, for the error paths that run after it. The earlier error paths never reach the insertion and keep using fail_ctrl: directly, so the list is only touched where the controller is actually on it. nvme_fc_ctrl_free() cannot use the plain "goto free_ctrl" the other transports use, because it still has to put_device(), release the rport reference and free the ida entry for resources taken before the insertion. Sample list_empty() under rport->lock instead. ctrl->ctrl.opts also stays valid for the whole teardown now. That is not the bug being fixed, but it removes some fragility around the old idiom: nvme_free_ctrl() calls nvme_auth_free() before ->free_ctrl(), and ctrl_max_dhchaps() dereferences ctrl->opts without a NULL check when ctrl->dhchap_ctxs is set, which nvme-fc permits since NVMF_ALLOWED_OPTS allows the dhchap options. The nvme sysfs attributes that dereference ctrl->opts, such as hostnqn and address, evaluate their is_visible() test once at device_add() time and stay readable until cdev_device_del().

References

Frequently Asked Questions

What is CVE-2026-89974?
CVE-2026-89974 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-89974?
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-89974?
CVE-2026-89974 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89974?
CVE-2026-89974 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89974?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6hqx-63gq-9x2p",
  "modified" : "2026-09-16T15:31:04Z",
  "published" : "2026-09-16T12:30:43Z",
  "aliases" : [ "CVE-2026-89974" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails\n\nnvmf_create_ctrl() owns the fabrics options and frees them whenever\n->create_ctrl() returns an error, so a transport must not free them on\nits own error paths.  nvme-fc tracks this by testing ctrl->ctrl.opts in\nnvme_fc_ctrl_free(), which requires nvme_fc_init_ctrl() to clear that\npointer on every error exit.\n\nThe coupling is implicit, and commit 1a9e218195a5 (\"nvme: split device\nadd from initialization\") broke it by adding a second error exit.  When\nnvme_add_ctrl() fails, nvme_fc_init_ctrl() jumps to out_put_ctrl:, past\nthe \"ctrl->ctrl.opts = NULL\" that only sits on the fail_ctrl: path, so\nnvme_fc_ctrl_free() frees the options and nvmf_create_ctrl() frees them\na second time:\n\n  BUG: KASAN: slab-use-after-free in nvmf_free_options+0x30/0x190\n   nvmf_free_options+0x30/0x190 drivers/nvme/host/fabrics.c:1284\n   nvmf_create_ctrl drivers/nvme/host/fabrics.c:1374 [inline]\n  Freed by task 5534:\n   nvme_fc_ctrl_free drivers/nvme/host/fc.c:2374 [inline]\n   nvme_fc_init_ctrl+0xe17/0x1450 drivers/nvme/host/fc.c:3605\n\nnvme_add_ctrl() fails when dev_set_name() cannot allocate, so this is\nreachable under memory pressure or fault injection.  Without KASAN the\noptions are freed twice.\n\nRather than clear the pointer on the second exit as well, derive\nownership the way nvme-tcp, nvme-rdma and nvme-loop do, from list\nmembership: their free_ctrl leaves the options alone unless the\ncontroller made it onto the transport list.\n\nThe list cannot simply be populated on the success path as it is there.\nnvme-fc runs the initial connect synchronously via flush_delayed_work(),\nand the controller has to be reachable on rport->ctrl_list for the whole\nof it: nvme_fc_unregister_remoteport() needs to find it to signal\nconnectivity loss, nvme_fc_match_disconn_ls() matches an incoming\nDisconnect Association LS against ctrl->association_id, which is only\nassigned during that window, nvme_fc_resume_controller() needs it on\nremoteport re-registration, and nvme_fc_existing_controller() uses it to\nreject a duplicate connect racing the one in flight.\n\nKeep the insertion where it is and add a fail_unlist: label, falling\ninto fail_ctrl:, for the error paths that run after it.  The earlier\nerror paths never reach the insertion and keep using fail_ctrl:\ndirectly, so the list is only touched where the controller is actually\non it.\n\nnvme_fc_ctrl_free() cannot use the plain \"goto free_ctrl\" the other\ntransports use, because it still has to put_device(), release the rport\nreference and free the ida entry for resources taken before the\ninsertion.  Sample list_empty() under rport->lock instead.\n\nctrl->ctrl.opts also stays valid for the whole teardown now.  That is\nnot the bug being fixed, but it removes some fragility around the old\nidiom: nvme_free_ctrl() calls nvme_auth_free() before ->free_ctrl(), and\nctrl_max_dhchaps() dereferences ctrl->opts without a NULL check when\nctrl->dhchap_ctxs is set, which nvme-fc permits since NVMF_ALLOWED_OPTS\nallows the dhchap options.  The nvme sysfs attributes that dereference\nctrl->opts, such as hostnqn and address, evaluate their is_visible()\ntest once at device_add() time and stay readable until\ncdev_device_del().",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89974"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/56e6279266f6962bb2d38a54397e3c605165b0c5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5f89d68c00ccd1b25151da0bf660012380c2bad9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7df913a7ced5d7349f0b23bdcf25ad54fe83a1c1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8bd14aa065112b4d523bea690027c7527a6224f6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:08Z"
  }
}