CVE-2026-89483: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-q8w5-3xh9-8fxf
Share
CVSS 7.5
Published
Advisory Summary

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

CVE Identifier CVE-2026-89483
GHSA Identifier GHSA-q8w5-3xh9-8fxf
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

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 High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-89483

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-89483, 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: zero the discard fallback page nvme_setup_discard() always maps sizeof(struct nvme_dsm_range) * NVME_DSM_MAX_RANGES = 4096 bytes as the DSM payload however many ranges the command declares, because some devices ignore the 'Number of Ranges' field - the Fixes: commit records two that read past the declared ranges. A single-range discard fills only the first 16 bytes. Normally the buffer comes from kzalloc() and the other 4080 bytes are zero. When that allocation fails the code falls back to the per-controller ctrl->discard_page, which nvme_init_ctrl() obtains with alloc_page(GFP_KERNEL) and nothing ever zeroes, so those 4080 bytes are whatever the page last held and are handed to the controller. Reaching it requires the kzalloc(GFP_ATOMIC | __GFP_NOWARN) to fail, that is memory pressure; it is not remotely triggerable. Failing the allocation under KMSAN reproduces it, with the leaked tail full of vmemmap struct page pointers. The extent in the report is a partial transfer of the payload, not the whole 4096 bytes; the 16-byte boundary in it is the one declared range: [ 11.991601] BUG: KMSAN: uninit-value in dma_map_phys+0x14c8/0x1900 [ 11.991969] dma_map_phys+0x14c8/0x1900 [ 11.992220] dma_map_page_attrs+0xcf/0x130 [ 11.992485] e1000_xmit_frame+0x4099/0x6d10 [ 11.992768] dev_hard_start_xmit+0x22f/0xa80 [ 11.993068] sch_direct_xmit+0x35c/0xcb0 [ 11.993315] __dev_queue_xmit+0x1ee5/0x5eb0 [ 11.993608] ip_finish_output2+0x1903/0x1c30 [ 11.993881] ip_finish_output+0x288/0x870 [ 11.994125] ip_output+0x15e/0x400 [ 11.994365] __ip_queue_xmit+0x1e85/0x1fb0 [ 11.994639] ip_queue_xmit+0x60/0x80 [ 11.994899] __tcp_transmit_skb+0x4e71/0x5fa0 [ 11.995210] tcp_write_xmit+0x3a36/0x9160 [ 11.995533] __tcp_push_pending_frames+0xc5/0x3c0 [ 11.995854] tcp_push+0x7dc/0x840 [ 11.996076] tcp_sendmsg_locked+0x766c/0x8400 [ 11.996371] tcp_sendmsg+0x4b/0x90 [ 11.996572] inet_sendmsg+0x134/0x2a0 [ 11.996823] __sock_sendmsg+0x265/0x360 [ 11.997076] sock_sendmsg+0x100/0x1e0 [ 11.997293] nvme_tcp_try_send+0x196f/0x6370 [ 11.997605] nvme_tcp_queue_rq+0x1d54/0x20b0 [ 11.997882] blk_mq_dispatch_rq_list+0x5ee/0x2e50 [ 11.998175] __blk_mq_sched_dispatch_requests+0x16dc/0x24a0 [ 11.998539] blk_mq_sched_dispatch_requests+0x11b/0x2c0 [ 11.998865] blk_mq_run_work_fn+0x13b/0x280 [ 11.999146] process_scheduled_works+0x966/0x1ad0 [ 11.999465] worker_thread+0xe44/0x1480 [ 11.999709] kthread+0x53b/0x600 [ 11.999927] ret_from_fork+0x29f/0x7c0 [ 12.000191] ret_from_fork_asm+0x1a/0x30 [ 12.000460] [ 12.000558] Uninit was created at: [ 12.000788] __alloc_frozen_pages_noprof+0x8bf/0xd30 [ 12.001096] alloc_pages_mpol+0x1d0/0x5f0 [ 12.001326] alloc_pages_noprof+0x102/0x290 [ 12.001627] nvme_init_ctrl+0x5a3/0x9f0 [ 12.001891] nvme_tcp_create_ctrl+0xd75/0x19b0 [ 12.002170] nvmf_dev_write+0x4c68/0x4fd0 [ 12.002426] vfs_write+0x587/0x1a10 [ 12.002636] __x64_sys_write+0x207/0x4f0 [ 12.002874] x64_sys_call+0x2ff0/0x3ea0 [ 12.003123] do_syscall_64+0x147/0x3b0 [ 12.003400] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 12.003680] [ 12.003777] Bytes 16-2843 of 2844 are uninitialized [ 12.004068] Memory access of size 2844 starts at ffff888109f82000 [ 12.004412] [ 12.004530] CPU: 0 UID: 0 PID: 101 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMECTL-gf5098b6bae76 #1 PREEMPT(lazy) [ 12.005127] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 12.005762] Workqueue: kblockd blk_mq_run_work_fn [ 12.006073] ===================================================== Allocate the page with __GFP_ZERO. The single allocation site covers every use of it: bytes no discard has written stay zero, and bytes one did write hold that controller's own range list, which it has already been sent.

References

NVD — CVE-2026-89483 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89483
git.kernel.org/stable/c/3f84d2bd0d... WEB
https://git.kernel.org/stable/c/3f84d2bd0d8ae8c7e8e0f8fc3cbf018a282971a1
git.kernel.org/stable/c/415f2772eb... WEB
https://git.kernel.org/stable/c/415f2772ebcbc7f3f1ab1a71915dab82cee3465e
git.kernel.org/stable/c/66b5af23b6... WEB
https://git.kernel.org/stable/c/66b5af23b6f956e57f8205c46aa80b054631be34
git.kernel.org/stable/c/67551d8430... WEB
https://git.kernel.org/stable/c/67551d8430df94c827e1830bd3a5fae1f66a5219
git.kernel.org/stable/c/76139b5bbf... WEB
https://git.kernel.org/stable/c/76139b5bbf531e675934b97227be3521c7fdd537
git.kernel.org/stable/c/bededeaaef... WEB
https://git.kernel.org/stable/c/bededeaaeff404978a5a8e2a605a6c3017cddd3e
git.kernel.org/stable/c/dc4d4b70a8... WEB
https://git.kernel.org/stable/c/dc4d4b70a863f7e39ef8bd137634be4e6db8b084
git.kernel.org/stable/c/f5827817b4... WEB
https://git.kernel.org/stable/c/f5827817b4fc7feeabf4f53fb4b626e6edc52fef

Frequently Asked Questions

What is CVE-2026-89483?
CVE-2026-89483 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-89483?
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-89483?
CVE-2026-89483 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-89483?
CVE-2026-89483 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89483?
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-q8w5-3xh9-8fxf",
  "modified" : "2026-09-14T15:32:26Z",
  "published" : "2026-09-11T21:31:28Z",
  "aliases" : [ "CVE-2026-89483" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme: zero the discard fallback page\n\nnvme_setup_discard() always maps sizeof(struct nvme_dsm_range) *\nNVME_DSM_MAX_RANGES = 4096 bytes as the DSM payload however many ranges\nthe command declares, because some devices ignore the 'Number of Ranges'\nfield - the Fixes: commit records two that read past the declared ranges.\nA single-range discard fills only the first 16 bytes.\n\nNormally the buffer comes from kzalloc() and the other 4080 bytes are\nzero.  When that allocation fails the code falls back to the\nper-controller ctrl->discard_page, which nvme_init_ctrl() obtains with\nalloc_page(GFP_KERNEL) and nothing ever zeroes, so those 4080 bytes are\nwhatever the page last held and are handed to the controller.  Reaching\nit requires the kzalloc(GFP_ATOMIC | __GFP_NOWARN) to fail, that is\nmemory pressure; it is not remotely triggerable.  Failing the allocation\nunder KMSAN reproduces it, with the leaked tail full of vmemmap struct\npage pointers.  The extent in the report is a partial transfer of the\npayload, not the whole 4096 bytes; the 16-byte boundary in it is the one\ndeclared range:\n\n[   11.991601] BUG: KMSAN: uninit-value in dma_map_phys+0x14c8/0x1900\n[   11.991969]  dma_map_phys+0x14c8/0x1900\n[   11.992220]  dma_map_page_attrs+0xcf/0x130\n[   11.992485]  e1000_xmit_frame+0x4099/0x6d10\n[   11.992768]  dev_hard_start_xmit+0x22f/0xa80\n[   11.993068]  sch_direct_xmit+0x35c/0xcb0\n[   11.993315]  __dev_queue_xmit+0x1ee5/0x5eb0\n[   11.993608]  ip_finish_output2+0x1903/0x1c30\n[   11.993881]  ip_finish_output+0x288/0x870\n[   11.994125]  ip_output+0x15e/0x400\n[   11.994365]  __ip_queue_xmit+0x1e85/0x1fb0\n[   11.994639]  ip_queue_xmit+0x60/0x80\n[   11.994899]  __tcp_transmit_skb+0x4e71/0x5fa0\n[   11.995210]  tcp_write_xmit+0x3a36/0x9160\n[   11.995533]  __tcp_push_pending_frames+0xc5/0x3c0\n[   11.995854]  tcp_push+0x7dc/0x840\n[   11.996076]  tcp_sendmsg_locked+0x766c/0x8400\n[   11.996371]  tcp_sendmsg+0x4b/0x90\n[   11.996572]  inet_sendmsg+0x134/0x2a0\n[   11.996823]  __sock_sendmsg+0x265/0x360\n[   11.997076]  sock_sendmsg+0x100/0x1e0\n[   11.997293]  nvme_tcp_try_send+0x196f/0x6370\n[   11.997605]  nvme_tcp_queue_rq+0x1d54/0x20b0\n[   11.997882]  blk_mq_dispatch_rq_list+0x5ee/0x2e50\n[   11.998175]  __blk_mq_sched_dispatch_requests+0x16dc/0x24a0\n[   11.998539]  blk_mq_sched_dispatch_requests+0x11b/0x2c0\n[   11.998865]  blk_mq_run_work_fn+0x13b/0x280\n[   11.999146]  process_scheduled_works+0x966/0x1ad0\n[   11.999465]  worker_thread+0xe44/0x1480\n[   11.999709]  kthread+0x53b/0x600\n[   11.999927]  ret_from_fork+0x29f/0x7c0\n[   12.000191]  ret_from_fork_asm+0x1a/0x30\n[   12.000460]\n[   12.000558] Uninit was created at:\n[   12.000788]  __alloc_frozen_pages_noprof+0x8bf/0xd30\n[   12.001096]  alloc_pages_mpol+0x1d0/0x5f0\n[   12.001326]  alloc_pages_noprof+0x102/0x290\n[   12.001627]  nvme_init_ctrl+0x5a3/0x9f0\n[   12.001891]  nvme_tcp_create_ctrl+0xd75/0x19b0\n[   12.002170]  nvmf_dev_write+0x4c68/0x4fd0\n[   12.002426]  vfs_write+0x587/0x1a10\n[   12.002636]  __x64_sys_write+0x207/0x4f0\n[   12.002874]  x64_sys_call+0x2ff0/0x3ea0\n[   12.003123]  do_syscall_64+0x147/0x3b0\n[   12.003400]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   12.003680]\n[   12.003777] Bytes 16-2843 of 2844 are uninitialized\n[   12.004068] Memory access of size 2844 starts at ffff888109f82000\n[   12.004412]\n[   12.004530] CPU: 0 UID: 0 PID: 101 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMECTL-gf5098b6bae76 #1 PREEMPT(lazy)\n[   12.005127] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   12.005762] Workqueue: kblockd blk_mq_run_work_fn\n[   12.006073] =====================================================\n\nAllocate the page with __GFP_ZERO.  The single allocation site covers\nevery use of it: bytes no discard has written stay zero, and bytes one\ndid write hold that controller's own range list, which it has already\nbeen sent.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89483"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3f84d2bd0d8ae8c7e8e0f8fc3cbf018a282971a1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/415f2772ebcbc7f3f1ab1a71915dab82cee3465e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/66b5af23b6f956e57f8205c46aa80b054631be34"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/67551d8430df94c827e1830bd3a5fae1f66a5219"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/76139b5bbf531e675934b97227be3521c7fdd537"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bededeaaeff404978a5a8e2a605a6c3017cddd3e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dc4d4b70a863f7e39ef8bd137634be4e6db8b084"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f5827817b4fc7feeabf4f53fb4b626e6edc52fef"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:29Z"
  }
}