CVE-2026-97525: x86/mm/pat: Allocate split page tables as kernel page tables

Published Sep 25, 2026
·
Updated

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 ptealloconekernel()) when the CPA code splits a large page (splitlargepage()).

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 (pagetablector() is never called thus neither is foliosetpgtable()) nor are statistics updated to reflect it (lruvecstataddfolio() is never called).

The latter issue of failing to mark the page table as a kernel page table (ptdescsetkernel() 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 pagetabledtorfree() if the PGtable folio flag for the ptdesc is set, otherwise we free the page table via pagetablefree().

Regardless of which path is taken page tables marked as kernel page tables, which now includes split page tables, take the correct route through pagetablefreekernel().

There is a user-visible side effect in that split page tables will appear in nrpagetablepages 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 ]

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch x86/mm/pat: Allocate split page tables as kernel page tables

Event History

Sep 25, 2026
CVE Published
via MITRE·10:21 AM
Data Sourced
via MITRE·10:21 AM
DescriptionSeverity
Data Sourced
via NVD·11:17 AM
DescriptionSeverity

Frequently Asked Questions

1

Which systems are implicated by this issue?

The issue concerns x86 Linux kernel systems in which the CPA code splits a large page. The supplied information does not identify affected kernel release versions.

2

Why does the missing page-table designation matter?

A split page table is freed without being marked as a kernel page table, so the kernel-page-table freeing path does not perform the associated IOTLB invalidation. Deferred freeing of kernel page tables makes this omission particularly significant.

3

How can I check whether a kernel source tree includes a fix?

Compare the source tree or distribution patch set against the fixes represented by stable commit IDs 84e0cd79d57f06b872154eb5d8f610584133f260, 922873cf4fc34124215070a8ad391bf831538bb9, and 9e4a3ec3411bb6bb59e3c1f29b75609f1e87aac4. The provided data does not map those fixes to kernel version numbers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203