CVE-2025-22045: x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs
In the Linux kernel, the following vulnerability has been resolved:
x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs
On the following path, flush_tlb_range() can be used for zapping normal
PMD entries (PMD entries that point to page tables) together with the PTE
entries in the pointed-to page table:
collapse_pte_mapped_thp
pmdp_collapse_flush
flush_tlb_range
The arm64 version of flush_tlb_range() has a comment describing that it can
be used for page table removal, and does not use any last-level
invalidation optimizations. Fix the X86 version by making it behave the
same way.
Currently, X86 only uses this information for the following two purposes,
which I think means the issue doesn't have much impact:
- In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be
IPI'd to avoid issues with speculative page table walks.
- In Hyper-V TLB paravirtualization, again for lazy TLB stuff.
The patch "x86/mm: only invalidate final translations with INVLPGB" which
is currently under review (see
<https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/>)
would probably be making the impact of this a lot worse.
Security readout for executives and security teams
Plain-English summary
A Linux x86 memory-management flaw may leave processor translation caches insufficiently cleared when certain page tables are removed. Exploitation requires local, low-privileged access; it is not described as remotely exploitable. Although scored 7.8, the kernel report says current impact appears limited.
Executive priority
Treat this as a scheduled high-priority kernel update, accelerated for shared x86 systems permitting untrusted local execution. It does not justify an internet-wide emergency response based on the supplied evidence, because access is local, active exploitation is not established, and the kernel description qualifies current impact as limited.
Technical view
During collapse_pte_mapped_thp, x86 flush_tlb_range() could zap a normal PMD and its PTEs without page-table-removal semantics. This affects lazy-TLB CPU notification and Hyper-V TLB paravirtualization behavior. Stable kernel commits change x86 invalidation to match arm64’s broader handling.
Likely exposure
Potentially exposed systems run affected x86 Linux kernels and permit untrusted local code or accounts. Hyper-V-hosted Linux workloads may warrant additional attention. The supplied version data does not provide complete distribution-package mappings, so administrators must verify exposure through their kernel or distribution vendor.
Exploitation context
The CVSS 3.1 score is 7.8 with local access and low privileges required. The supplied record is not in KEV and provides no evidence of active exploitation or a public working exploit. The original technical description characterizes present impact as limited but warns that later invalidation optimizations could worsen it.
Researcher notes
Key review areas are normal-PMD removal, speculative page-table walks on lazy-TLB CPUs, and Hyper-V paravirtualized invalidation. The source warns that a separately reviewed INVLPGB optimization could increase impact, but the bundle does not establish that change as deployed or affected. No exploitability demonstration or detailed failure outcome is supplied.
Mitigation direction
Upgrade to a vendor-supported kernel containing the cited stable fix.
Reboot after installation so the corrected kernel is running.
Prioritize x86 multi-user systems and Hyper-V Linux workloads.
If updates are unavailable, restrict untrusted local access and consult vendor guidance.
Validation and detection
Inventory running kernels, architectures, distribution packages, and virtualization environments.
Compare each kernel package against its vendor advisory and cited stable fix.
After reboot, confirm the active kernel is the corrected package.
Document systems whose vendor has not supplied definitive affected-version mapping.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-22045 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
12Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.