CVE-2026-89966: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-j92g-qm8v-9jw7

Published 2026-09-16

Advisory Summary

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

CVE Identifier CVE-2026-89966

GHSA Identifier GHSA-j92g-qm8v-9jw7

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-16

Last Updated 2026-09-16

How to Fix CVE-2026-89966

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-89966, 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: mm/hugetlb_cma: fix null nodemask dereference in hugetlb_cma_alloc_frozen_folio alloc_buddy_hugetlb_folio_with_mpol() can pass a NULL nodemask to alloc_fresh_hugetlb_folio() as a fallback to allocate from all nodes. If order is gigantic, alloc_fresh_hugetlb_folio() propagates the NULL nodemask down to hugetlb_cma_alloc_frozen_folio() via alloc_gigantic_frozen_folio(). Additionally, hugetlb_cma_alloc_frozen_folio() previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding a node_isset(nid, *nodemask) check ensures the initial preferred node allocation honors the memory policy / nodemask. However, hugetlb_cma_alloc_frozen_folio() dereferences the nodemask in node_isset(nid, *nodemask) and for_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL. Fix this by checking if nodemask is NULL in hugetlb_cma_alloc_frozen_folio() and defaulting it to cpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures. From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with MPOL_PREFERRED_MANY on a system where CMA is only configured on a subset of NUMA nodes. This can be reproduced by booting a VM with two NUMA nodes, restricting CMA to Node 1 (e.g., hugetlb_cma=1:1G default_hugepagesz=1G hugepagesz=1G hugepages=0), and running a program that allocates a 1GB hugepage area without reserving, restricts allocation to Node 0 using mbind() with MPOL_PREFERRED_MANY, and triggers a page fault: void *ptr = mmap(NULL, 1UL << 30, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB | MAP_HUGE_1GB | MAP_NORESERVE, -1, 0); unsigned long nodemask = 1; /* Node 0 */ mbind(ptr, 1UL << 30, MPOL_PREFERRED_MANY, &nodemask, sizeof(nodemask) * 8, 0); memset(ptr, 0, 1UL << 30); /* Trigger fault */ This results in a NULL pointer dereference: BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:hugetlb_cma_alloc_frozen_folio+0x75/0x120 Call Trace: <TASK> only_alloc_fresh_hugetlb_folio.isra.0+0x2c/0x160 alloc_surplus_hugetlb_folio+0x6d/0x100 alloc_hugetlb_folio+0x3c5/0x660 hugetlb_no_page+0x3d9/0x650

References

NVD — CVE-2026-89966 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-89966

git.kernel.org/stable/c/10f616ef06... WEB

https://git.kernel.org/stable/c/10f616ef06c5bd2d656a0eebaf73f9b09d150c24

git.kernel.org/stable/c/7b8a8ae4dd... WEB

https://git.kernel.org/stable/c/7b8a8ae4dd176a232e973017d2aa3c536a7275e2

Frequently Asked Questions

What is CVE-2026-89966?

CVE-2026-89966 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-89966?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2026-89966?

CVE-2026-89966 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-89966?

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-j92g-qm8v-9jw7",
  "modified" : "2026-09-16T12:30:43Z",
  "published" : "2026-09-16T12:30:43Z",
  "aliases" : [ "CVE-2026-89966" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb_cma: fix null nodemask dereference in hugetlb_cma_alloc_frozen_folio\n\nalloc_buddy_hugetlb_folio_with_mpol() can pass a NULL nodemask to\nalloc_fresh_hugetlb_folio() as a fallback to allocate from all nodes.  If\norder is gigantic, alloc_fresh_hugetlb_folio() propagates the NULL\nnodemask down to hugetlb_cma_alloc_frozen_folio() via\nalloc_gigantic_frozen_folio().\n\nAdditionally, hugetlb_cma_alloc_frozen_folio() previously attempted\nallocation on hugetlb_cma[nid] without verifying if nid is included in the\ncaller's nodemask.  Adding a node_isset(nid, *nodemask) check ensures the\ninitial preferred node allocation honors the memory policy / nodemask.\n\nHowever, hugetlb_cma_alloc_frozen_folio() dereferences the nodemask in\nnode_isset(nid, *nodemask) and for_each_node_mask(node, *nodemask),\nleading to a null pointer dereference kernel panic when nodemask is NULL.\n\nFix this by checking if nodemask is NULL in\nhugetlb_cma_alloc_frozen_folio() and defaulting it to\ncpuset_current_mems_allowed.  Enclose the allocation attempts within the\ncpuset seqcount retry loop so that if the cpuset changes concurrently\nduring allocation, the attempts are retried using the updated nodemask. \nThis ensures that the initial node check and fallback loop safely honor\nthe task's cpuset without violating cpuset constraints or causing NULL\npointer dereferences or unexpected allocation failures.\n\nFrom a userspace perspective, this bug allows an unprivileged user to\ncrash the kernel (trigger a panic) by requesting a gigantic hugepage\nallocation with MPOL_PREFERRED_MANY on a system where CMA is only\nconfigured on a subset of NUMA nodes.\n\nThis can be reproduced by booting a VM with two NUMA nodes, restricting\nCMA to Node 1 (e.g., hugetlb_cma=1:1G default_hugepagesz=1G hugepagesz=1G\nhugepages=0), and running a program that allocates a 1GB hugepage area\nwithout reserving, restricts allocation to Node 0 using mbind() with\nMPOL_PREFERRED_MANY, and triggers a page fault:\n\n  void *ptr = mmap(NULL, 1UL << 30, PROT_READ | PROT_WRITE,\n                   MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB |\n                   MAP_HUGE_1GB | MAP_NORESERVE, -1, 0);\n  unsigned long nodemask = 1; /* Node 0 */\n  mbind(ptr, 1UL << 30, MPOL_PREFERRED_MANY, &nodemask,\n        sizeof(nodemask) * 8, 0);\n  memset(ptr, 0, 1UL << 30); /* Trigger fault */\n\nThis results in a NULL pointer dereference:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  RIP: 0010:hugetlb_cma_alloc_frozen_folio+0x75/0x120\n  Call Trace:\n   <TASK>\n   only_alloc_fresh_hugetlb_folio.isra.0+0x2c/0x160\n   alloc_surplus_hugetlb_folio+0x6d/0x100\n   alloc_hugetlb_folio+0x3c5/0x660\n   hugetlb_no_page+0x3d9/0x650",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89966"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/10f616ef06c5bd2d656a0eebaf73f9b09d150c24"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7b8a8ae4dd176a232e973017d2aa3c536a7275e2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:07Z"
  }
}

Advisory Metadata

Source ID: GHSA-j92g-qm8v-9jw7
Schema Version: 1.4.0
Published: 2026-09-16 12:30
Last Modified: 2026-09-16 12:30
Database Record File: advisories/unreviewed/2026/09/GHSA-j92g-qm8v-9jw7/GHSA-j92g-qm8v-9jw7.json