CVE-2026-97945: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-pxx4-gwjw-xj68
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97945
GHSA Identifier GHSA-pxx4-gwjw-xj68
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-97945

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-97945, 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: x86/mm: Fix user-space data loss with MADV_FREE and THP Some of users of Polars (a data analytics library) have lost production data from this bug. They seem to have just the right combination of huge pages, MADV_FREE and heavy reclaim pressure. pmd_modify() masks the old value with (_HPAGE_CHG_MASK & ~_PAGE_DIRTY), silently discarding the hardware dirty bit. The subsequent pmd_mksaveddirty() call is supposed to transfer _PAGE_DIRTY into _PAGE_SAVED_DIRTY when write-protecting, but the dirty bit was already stripped from the value, so there is nothing left to transfer. Contrast with pte_modify(), which keeps _PAGE_DIRTY_BITS in its mask, and pud_modify(), which keeps _HPAGE_CHG_MASK untouched: pmd_modify() is the odd one out. Any pmd_modify() on a writable, dirty PMD loses the dirty state. One visible consequence is data loss with MADV_FREE on PMD-mapped THP: memset(buf, 0x5A, size); // PMD-mapped THP, PMD dirty madvise(buf, size, MADV_FREE); // PMD cleaned but left writable, // folio marked lazyfree memset(buf, 0x5A, size); // hardware sets _PAGE_DIRTY again mprotect(buf, size, PROT_READ); // pmd_modify() drops the dirty bit mprotect(buf, size, PROT_READ|PROT_WRITE); // ... memory pressure ... Reclaim (e.g. under memcg pressure) then finds the lazyfree folio with no dirty bit set anywhere and frees it in __discard_anon_folio_pmd_locked(), even though the data was rewritten after MADV_FREE; subsequent reads fault in fresh zero pages. NUMA hinting alone can trigger the same loss, as do_huge_pmd_numa_page() restores the PMD through pmd_modify() as well. PMD-mapped file THPs are affected too: mprotect()/NUMA hinting dropping the dirty bit means rewritten data is never written back. Fix it by keeping _PAGE_DIRTY in the preserved mask, exactly like pte_modify() and pud_modify() do. The existing pmd_mksaveddirty()/pmd_clear_saveddirty() pair then performs the hardware-dirty <-> saved-dirty transition based on the write bit, preserving the shadow-stack encoding rules.

References

NVD — CVE-2026-97945 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97945
git.kernel.org/stable/c/55ddbc2ca6... WEB
https://git.kernel.org/stable/c/55ddbc2ca6d5db64d44c3fb8f8705b4d39eb30b7
git.kernel.org/stable/c/a5ad97cbcf... WEB
https://git.kernel.org/stable/c/a5ad97cbcfcec31430268441c10eedde73200177
git.kernel.org/stable/c/b5dec6dfb5... WEB
https://git.kernel.org/stable/c/b5dec6dfb593d81fec15ba43c4fe5d58f10a49a2
git.kernel.org/stable/c/e4d569fe2f... WEB
https://git.kernel.org/stable/c/e4d569fe2f436a9b58c048fefabf56eab68c1b7e
git.kernel.org/stable/c/f7491d7c81... WEB
https://git.kernel.org/stable/c/f7491d7c81db0e7c304a7bd757a76d2fbeaff80e

Frequently Asked Questions

What is CVE-2026-97945?
CVE-2026-97945 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-97945?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97945?
CVE-2026-97945 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97945?
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-pxx4-gwjw-xj68",
  "modified" : "2026-10-03T12:31:21Z",
  "published" : "2026-09-25T12:31:29Z",
  "aliases" : [ "CVE-2026-97945" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm: Fix user-space data loss with MADV_FREE and THP\n\nSome of users of Polars (a data analytics library) have lost production\ndata from this bug. They seem to have just the right combination of\nhuge pages, MADV_FREE and heavy reclaim pressure.\n\npmd_modify() masks the old value with (_HPAGE_CHG_MASK & ~_PAGE_DIRTY),\nsilently discarding the hardware dirty bit.  The subsequent\npmd_mksaveddirty() call is supposed to transfer _PAGE_DIRTY into\n_PAGE_SAVED_DIRTY when write-protecting, but the dirty bit was already\nstripped from the value, so there is nothing left to transfer.\n\nContrast with pte_modify(), which keeps _PAGE_DIRTY_BITS in its mask,\nand pud_modify(), which keeps _HPAGE_CHG_MASK untouched: pmd_modify()\nis the odd one out.  Any pmd_modify() on a writable, dirty PMD loses\nthe dirty state.\n\nOne visible consequence is data loss with MADV_FREE on PMD-mapped THP:\n\n    memset(buf, 0x5A, size);          // PMD-mapped THP, PMD dirty\n    madvise(buf, size, MADV_FREE);    // PMD cleaned but left writable,\n                                      // folio marked lazyfree\n    memset(buf, 0x5A, size);          // hardware sets _PAGE_DIRTY again\n    mprotect(buf, size, PROT_READ);   // pmd_modify() drops the dirty bit\n    mprotect(buf, size, PROT_READ|PROT_WRITE);\n    // ... memory pressure ...\n\nReclaim (e.g. under memcg pressure) then finds the lazyfree folio with\nno dirty bit set anywhere and frees it in\n__discard_anon_folio_pmd_locked(), even though the data was rewritten\nafter MADV_FREE; subsequent reads fault in fresh zero pages.  NUMA\nhinting alone can trigger the same loss, as do_huge_pmd_numa_page()\nrestores the PMD through pmd_modify() as well.\n\nPMD-mapped file THPs are affected too: mprotect()/NUMA hinting dropping\nthe dirty bit means rewritten data is never written back.\n\nFix it by keeping _PAGE_DIRTY in the preserved mask, exactly like\npte_modify() and pud_modify() do.  The existing\npmd_mksaveddirty()/pmd_clear_saveddirty() pair then performs the\nhardware-dirty <-> saved-dirty transition based on the write bit,\npreserving the shadow-stack encoding rules.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97945"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55ddbc2ca6d5db64d44c3fb8f8705b4d39eb30b7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a5ad97cbcfcec31430268441c10eedde73200177"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b5dec6dfb593d81fec15ba43c4fe5d58f10a49a2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e4d569fe2f436a9b58c048fefabf56eab68c1b7e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f7491d7c81db0e7c304a7bd757a76d2fbeaff80e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:21Z"
  }
}