{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97945 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-97945 is a vulnerability in Linux, published on 25 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-97945 and fix it if it is affected.\n\nWhat it is: CVE-2026-97945 is a vulnerability in Linux, published on 25 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-97945 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97945/ (Markdown: https://insights.sbomify.com/CVE-2026-97945/index.md)","id":"CVE-2026-97945","markdown":"https://insights.sbomify.com/CVE-2026-97945/index.md","name":"CVE-2026-97945","record":{"aliases":["AZL-104843","BELL-CVE-2026-97945","DEBIAN-CVE-2026-97945","GHSA-pxx4-gwjw-xj68","UBUNTU-CVE-2026-97945"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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 \u0026 ~_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 \u003c-\u003e saved-dirty transition based on the write bit,\npreserving the shadow-stack encoding rules.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"x86/mm: Fix user-space data loss with MADV_FREE and THP","id":"CVE-2026-97945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"x86/amd_node: Fix PCI device reference counting in amd_smn_init()","id":"CVE-2026-97946"},"packages":[],"prev":{"headline":"x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()","id":"CVE-2026-97944"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-97945/"}