Menu

Star on GitHub · 3.2k

CVE-2026-31397

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix use of NULL folio in move_pages_huge_pmd() move_pages_huge_pmd() handles UFFDIO_MOVE for both normal THPs a…

Published Apr 3, 2026CWE-476EPSS 0.17%

Overview

CVE-2026-31397 is a high-severity vulnerability. It was published on April 3, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mm/huge_memory: fix use of NULL folio in move_pages_huge_pmd()

move_pages_huge_pmd() handles UFFDIO_MOVE for both normal THPs and huge

zero pages. For the huge zero page path, src_folio is explicitly set to

NULL, and is used as a sentinel to skip folio operations like lock and

rmap.

In the huge zero page branch, src_folio is NULL, so folio_mk_pmd(NULL,

pgprot) passes NULL through folio_pfn() and page_to_pfn(). With

SPARSEMEM_VMEMMAP this silently produces a bogus PFN, installing a PMD

pointing to non-existent physical memory. On other memory models it is a

NULL dereference.

Use page_folio(src_page) to obtain the valid huge zero folio from the

page, which was obtained from pmd_page() and remains valid throughout.

After commit d82d09e48219 ("mm/huge_memory: mark PMD mappings of the huge

zero folio special"), moved huge zero PMDs must remain special so

vm_normal_page_pmd() continues to treat them as special mappin

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31397?

CVE-2026-31397 is a high-severity vulnerability. It was published on April 3, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31397?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31397?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31397?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31397 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all