CVE-2026-89758: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-rw23-9h76-pf6x
Share
CVSS 7.8
Published
Advisory Summary

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

CVE-2026-89758 at a Glance

CVE Identifier CVE-2026-89758
GHSA Identifier GHSA-rw23-9h76-pf6x
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

How to Fix CVE-2026-89758

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-89758, 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/mempolicy: skip non-present PMDs when queueing folios Patch series "mm: handle device-private PMDs in walk callbacks", v3. Since commit 368076f52ebe ("mm/huge_memory: add device-private THP support to PMD operations") a PMD may hold a device-private swap entry whenever an HMM-based GPU driver migrates an anonymous THP folio to device memory via migrate_vma_pages(). pmd_trans_huge_lock() succeeds for such PMDs (pmd_is_huge() returns true for any non-present, non-none huge PMD), so several MM walk callbacks that used to assume present THP or migration entry are now reachable with a device-private PMD. The results range from a VM_BUG_ON() firing on debug kernels, to an oops on a bogus vmemmap dereference, to silently isolating an unrelated live folio from LRU in the aliasing case. This patch (of 3): queue_folios_pmd() is called under pmd_trans_huge_lock(), whose pmd_is_huge() check returns true for any non-present, non-none PMD softleaf. Passing such a PMD to pmd_folio() treats the softleaf encoding as a hardware PFN and can return a bogus folio pointer. Mirror queue_folios_pte_range(): handle non-present entries before looking up a folio. Keep migration entries counted as failures, but skip other non-present PMDs such as device-private entries. Potential trigger: an HMM-based GPU driver migrates an anonymous THP folio to device memory via migrate_vma_pages(), leaving a device-private PMD. Userspace then calls mbind(), migrate_pages() or set_mempolicy_home_node() on that range.

References

NVD — CVE-2026-89758 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89758
git.kernel.org/stable/c/2858b4027f... WEB
https://git.kernel.org/stable/c/2858b4027f491e6fdb8ee2d8923798b619bf2791
git.kernel.org/stable/c/3d927093b2... WEB
https://git.kernel.org/stable/c/3d927093b2add7ced588a926c3dc5d7a83f18596

Frequently Asked Questions

What is CVE-2026-89758?
CVE-2026-89758 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-89758?
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-89758?
CVE-2026-89758 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89758?
CVE-2026-89758 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89758?
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-rw23-9h76-pf6x",
  "modified" : "2026-09-13T09:32:30Z",
  "published" : "2026-09-11T21:31:39Z",
  "aliases" : [ "CVE-2026-89758" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempolicy: skip non-present PMDs when queueing folios\n\nPatch series \"mm: handle device-private PMDs in walk callbacks\", v3.\n\nSince commit 368076f52ebe (\"mm/huge_memory: add device-private THP support\nto PMD operations\") a PMD may hold a device-private swap entry whenever an\nHMM-based GPU driver migrates an anonymous THP folio to device memory via\nmigrate_vma_pages().\n\npmd_trans_huge_lock() succeeds for such PMDs (pmd_is_huge() returns true\nfor any non-present, non-none huge PMD), so several MM walk callbacks that\nused to assume present THP or migration entry are now reachable with a\ndevice-private PMD.  The results range from a VM_BUG_ON() firing on debug\nkernels, to an oops on a bogus vmemmap dereference, to silently isolating\nan unrelated live folio from LRU in the aliasing case.\n\n\nThis patch (of 3):\n\nqueue_folios_pmd() is called under pmd_trans_huge_lock(), whose\npmd_is_huge() check returns true for any non-present, non-none PMD\nsoftleaf.  Passing such a PMD to pmd_folio() treats the softleaf encoding\nas a hardware PFN and can return a bogus folio pointer.\n\nMirror queue_folios_pte_range(): handle non-present entries before looking\nup a folio.  Keep migration entries counted as failures, but skip other\nnon-present PMDs such as device-private entries.\n\nPotential trigger: an HMM-based GPU driver migrates an anonymous THP folio\nto device memory via migrate_vma_pages(), leaving a device-private PMD. \nUserspace then calls mbind(), migrate_pages() or set_mempolicy_home_node()\non that range.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89758"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2858b4027f491e6fdb8ee2d8923798b619bf2791"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3d927093b2add7ced588a926c3dc5d7a83f18596"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:06Z"
  }
}