CVE-2026-97525
Received Received - Intake

Page Table Allocation Flaw in Linux Kernel

Vulnerability report for CVE-2026-97525, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-09-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Allocate split page tables as kernel page tables A PTE is allocated directly without going through the standard page table allocation routines (such as pte_alloc_one_kernel()) when the CPA code splits a large page (__split_large_page()). This means the page table constructor is never called nor is the page table marked as a kernel page table. The former results in the folio associated with the page table not being marked as a page table (__pagetable_ctor() is never called thus neither is __folio_set_pgtable()) nor are statistics updated to reflect it (lruvec_stat_add_folio() is never called). The latter issue of failing to mark the page table as a kernel page table (ptdesc_set_kernel() is never called) is far more problematic. Since commit: 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page tables") kernel page table freeing has been batched and since the subsequent commit: e37d5a2d60a3 ("iommu/sva: invalidate stale IOTLB entries for kernel address space") IOTLB cache entries for kernel page tables have been invalidated upon being freed. Since split page tables are freed without this invalidation, the IOTLB can contain stale entries for them. Resolve the issue by using the ordinary PTE allocation API at split time. This results in these kernel page tables invoking a page table constructor, and thus requires a page table destructor. Destructors are not always present, like for early allocated direct map page tables). Conditionally call pagetable_dtor_free() if the PG_table folio flag for the ptdesc is set, otherwise we free the page table via pagetable_free(). Regardless of which path is taken page tables marked as kernel page tables, which now includes split page tables, take the correct route through pagetable_free_kernel(). There is a user-visible side effect in that split page tables will appear in nr_page_table_pages in /proc/vmstat (as do other kernel page tables allocated after early boot), however this is a positive change. This issue started being markedly problematic after commit: 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page tables") so choose this as the Fixes target. [ dhansen: rephrase in imperative mood ]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-09-25
Generated
2026-09-25
AI Q&A
2026-09-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper handling of page tables when splitting large pages. Normally, page tables are allocated using standard routines that mark them as kernel page tables and initialize them correctly. However, in this case, the page table constructor is skipped, and the page table is not marked as a kernel page table. This leads to issues where the page table is freed without invalidating IOTLB cache entries, potentially causing stale entries and system instability.

Detection Guidance

This vulnerability is specific to the Linux kernel's memory management and requires kernel-level inspection. Detection involves checking kernel logs for related errors or verifying if your kernel version includes the fix. Commands like 'dmesg | grep -i page' or 'cat /proc/version' may help identify kernel details. However, no direct detection commands are provided in the CVE details.

Impact Analysis

The impact includes potential system crashes or instability due to stale IOTLB entries in the memory management unit. Split page tables may not be properly tracked or freed, leading to memory leaks or incorrect memory management. Users may notice increased memory usage or performance degradation.

Mitigation Strategies

Apply the kernel patch or update to a version that includes the fix for CVE-2026-97525. Monitor kernel logs for errors related to page table handling. Ensure your system is running a patched kernel version to prevent potential IOTLB cache issues.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97525. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart