CVE-2026-89596: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-2x8h-gf2x-f48m
Share
CVSS 7.1
Published
Advisory Summary

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

CVE-2026-89596 at a Glance

CVE Identifier CVE-2026-89596
GHSA Identifier GHSA-2x8h-gf2x-f48m
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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

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

How to Fix CVE-2026-89596

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-89596, 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: forcedeth: fix off-by-one when saving/restoring non-PCI config space nv_suspend() and nv_resume() walk the non-PCI configuration space with for (i = 0; i <= np->register_size/sizeof(u32); i++) which runs one iteration too many. saved_config_space is declared as u32 saved_config_space[NV_PCI_REGSZ_MAX/4]; and NV_PCI_REGSZ_VER3 is equal to NV_PCI_REGSZ_MAX (0x604), so on a VER3 device register_size/sizeof(u32) is exactly the array length and the last iteration addresses one element past the end. The element it lands on is np->name_rx[0..3]: saved_config_space[] is followed immediately by char name_rx[IFNAMSIZ + 3], and char needs no padding. Nothing observable is corrupted by that, because nv_request_irq() rewrites name_rx with sprintf() before it is ever passed to request_irq(). The bug is the out-of-bounds access itself, which UBSAN reports and which CONFIG_UBSAN_TRAP=y turns into a trap that aborts the running kernel code, plus an MMIO read and, on resume, an MMIO writel() to base + 0x604, one dword past the range the driver mapped: np->base = ioremap(addr, np->register_size); VER1 and VER2 devices stay inside the array, but they too get the stray read and the stray write one dword past their own window. Caught by UBSAN on an Apple Macmini3,1 (MCP79) during a deep S3 cycle. The splat below is trimmed: the build path in the file name, the CPU and taint lines, the Workqueue line, the "?" hint frames, and the frames below device_suspend are all cut. The kernel was tainted, with an out-of-tree nouveau and CPU_OUT_OF_SPEC; forcedeth itself was the stock module. UBSAN: array-index-out-of-bounds in drivers/net/ethernet/nvidia/forcedeth.c:6225:25 index 385 is out of range for type 'u32 [385]' Call Trace: dump_stack_lvl+0x5d/0x80 ubsan_epilogue+0x5/0x2b __ubsan_handle_out_of_bounds.cold+0x54/0x59 __this_module+0xe398c/0xe9010 [forcedeth] pci_pm_suspend+0x80/0x170 dpm_run_callback+0x51/0x160 device_suspend+0x1a2/0x4a0 ... Both loops are hit. UBSAN reports each source location only once per module load (__ubsan_handle_out_of_bounds() calls suppress_report(), which does test_and_set_bit(REPORTED_BIT, ...) on the struct source_location), so the two splats land in the first S3 cycle after the module is loaded and later cycles are silent even though the access still runs off the end every time. In that first cycle line 6225 is reported from pci_pm_suspend and line 6240 from pci_pm_resume. The same off-by-one was fixed in nv_get_regs() by commit ba9aa134287f ("forcedeth: fix buffer overflow") in 2012; these two loops were missed. The suspend and resume side was reported on LKML in September 2013 by Marc Weber, with the same analysis and the same one-character fix, but the patch was attached rather than sent inline and the thread ended there. Use < instead of <=, which saves and restores exactly register_size bytes.

References

NVD — CVE-2026-89596 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89596
git.kernel.org/stable/c/0c3f4544ff... WEB
https://git.kernel.org/stable/c/0c3f4544ff3873594c8af1b907b4ac4e6d5ce005
git.kernel.org/stable/c/702aa4a44c... WEB
https://git.kernel.org/stable/c/702aa4a44c87026b97b1da5c5ca80e1fa8a9875a
git.kernel.org/stable/c/9379f8527c... WEB
https://git.kernel.org/stable/c/9379f8527ca60d92715c90b32f1b477de9ec32cb
git.kernel.org/stable/c/9393f1d656... WEB
https://git.kernel.org/stable/c/9393f1d656a79693e0c123ff7bc7c5c0f708046d
git.kernel.org/stable/c/c4d5953582... WEB
https://git.kernel.org/stable/c/c4d5953582463f45e48b14ef9815e5fb636f7e1f
git.kernel.org/stable/c/c4f196bfee... WEB
https://git.kernel.org/stable/c/c4f196bfeedd71e56aba4b63bd8f919edb2f7056
git.kernel.org/stable/c/effd589568... WEB
https://git.kernel.org/stable/c/effd589568b2c4399894a23000286210c60af6d7
git.kernel.org/stable/c/fc71c6c3d3... WEB
https://git.kernel.org/stable/c/fc71c6c3d3e3bb17474dcd1162aea6783a452a64

Frequently Asked Questions

What is CVE-2026-89596?
CVE-2026-89596 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-89596?
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-89596?
CVE-2026-89596 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-89596?
CVE-2026-89596 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89596?
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-2x8h-gf2x-f48m",
  "modified" : "2026-09-14T15:32:30Z",
  "published" : "2026-09-11T21:31:33Z",
  "aliases" : [ "CVE-2026-89596" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nforcedeth: fix off-by-one when saving/restoring non-PCI config space\n\nnv_suspend() and nv_resume() walk the non-PCI configuration space with\n\n\tfor (i = 0; i <= np->register_size/sizeof(u32); i++)\n\nwhich runs one iteration too many. saved_config_space is declared as\n\n\tu32 saved_config_space[NV_PCI_REGSZ_MAX/4];\n\nand NV_PCI_REGSZ_VER3 is equal to NV_PCI_REGSZ_MAX (0x604), so on a VER3\ndevice register_size/sizeof(u32) is exactly the array length and the last\niteration addresses one element past the end.\n\nThe element it lands on is np->name_rx[0..3]: saved_config_space[] is\nfollowed immediately by char name_rx[IFNAMSIZ + 3], and char needs no\npadding. Nothing observable is corrupted by that, because nv_request_irq()\nrewrites name_rx with sprintf() before it is ever passed to request_irq().\nThe bug is the out-of-bounds access itself, which UBSAN reports and which\nCONFIG_UBSAN_TRAP=y turns into a trap that aborts the running kernel code,\nplus an MMIO read and, on resume, an MMIO writel() to base + 0x604, one\ndword past the range the driver mapped:\n\n\tnp->base = ioremap(addr, np->register_size);\n\nVER1 and VER2 devices stay inside the array, but they too get the stray\nread and the stray write one dword past their own window.\n\nCaught by UBSAN on an Apple Macmini3,1 (MCP79) during a deep S3 cycle.\nThe splat below is trimmed: the build path in the file name, the CPU\nand taint lines, the Workqueue line, the \"?\" hint frames, and the\nframes below device_suspend are all cut. The kernel was tainted, with\nan out-of-tree nouveau and CPU_OUT_OF_SPEC; forcedeth itself was the\nstock module.\n\n  UBSAN: array-index-out-of-bounds in drivers/net/ethernet/nvidia/forcedeth.c:6225:25\n  index 385 is out of range for type 'u32 [385]'\n  Call Trace:\n   dump_stack_lvl+0x5d/0x80\n   ubsan_epilogue+0x5/0x2b\n   __ubsan_handle_out_of_bounds.cold+0x54/0x59\n   __this_module+0xe398c/0xe9010 [forcedeth]\n   pci_pm_suspend+0x80/0x170\n   dpm_run_callback+0x51/0x160\n   device_suspend+0x1a2/0x4a0\n   ...\n\nBoth loops are hit. UBSAN reports each source location only once per module\nload (__ubsan_handle_out_of_bounds() calls suppress_report(), which does\ntest_and_set_bit(REPORTED_BIT, ...) on the struct source_location), so the\ntwo splats land in the first S3 cycle after the module is loaded and later\ncycles are silent even though the access still runs off the end every time.\nIn that first cycle line 6225 is reported from pci_pm_suspend and line 6240\nfrom pci_pm_resume.\n\nThe same off-by-one was fixed in nv_get_regs() by commit ba9aa134287f\n(\"forcedeth: fix buffer overflow\") in 2012; these two loops were missed.\nThe suspend and resume side was reported on LKML in September 2013 by Marc\nWeber, with the same analysis and the same one-character fix, but the patch\nwas attached rather than sent inline and the thread ended there.\n\nUse < instead of <=, which saves and restores exactly register_size bytes.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89596"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0c3f4544ff3873594c8af1b907b4ac4e6d5ce005"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/702aa4a44c87026b97b1da5c5ca80e1fa8a9875a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9379f8527ca60d92715c90b32f1b477de9ec32cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9393f1d656a79693e0c123ff7bc7c5c0f708046d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c4d5953582463f45e48b14ef9815e5fb636f7e1f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c4f196bfeedd71e56aba4b63bd8f919edb2f7056"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/effd589568b2c4399894a23000286210c60af6d7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fc71c6c3d3e3bb17474dcd1162aea6783a452a64"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:44Z"
  }
}