Answer in brief
CVE-2025-22045 records a Unknown severity vulnerability in x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-22045 records a Unknown severity vulnerability in x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=016c4d92cd16f569c6485ae62b076c1a4b779536 <618d5612ecb7bfc1c85342daafeb2b47e29e77a3 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <556d446068f90981e5d71ca686bdaccdd545d491 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <0a8f806ea6b5dd64b3d1f05ff774817d5f7ddbd1 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <0708fd6bd8161871bfbadced2ca4319b84ab44fe || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <7085895c59e4057ffae17f58990ccb630087d0d2 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <93224deb50a8d20df3884f3672ce9f982129aa50 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <320ac1af4c0bdb92c864dc9250d1329234820edf || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <78d6f9a9eb2a5da6fcbd76d6191d24b0dcc321be || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <3ef938c3503563bfc2ac15083557f880d29c2e64 | 618d5612ecb7bfc1c85342daafeb2b47e29e77a3, 556d446068f90981e5d71ca686bdaccdd545d491, 0a8f806ea6b5dd64b3d1f05ff774817d5f7ddbd1, 0708fd6bd8161871bfbadced2ca4319b84ab44fe, 7085895c59e4057ffae17f58990ccb630087d0d2, 93224deb50a8d20df3884f3672ce9f982129aa50, 320ac1af4c0bdb92c864dc9250d1329234820edf, 78d6f9a9eb2a5da6fcbd76d6191d24b0dcc321be, 3ef938c3503563bfc2ac15083557f880d29c2e64 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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/[email protected]/>) would probably be making the impact of this a lot worse.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=016c4d92cd16f569c6485ae62b076c1a4b779536 <618d5612ecb7bfc1c85342daafeb2b47e29e77a3 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <556d446068f90981e5d71ca686bdaccdd545d491 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <0a8f806ea6b5dd64b3d1f05ff774817d5f7ddbd1 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <0708fd6bd8161871bfbadced2ca4319b84ab44fe || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <7085895c59e4057ffae17f58990ccb630087d0d2 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <93224deb50a8d20df3884f3672ce9f982129aa50 || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <320ac1af4c0bdb92c864dc9250d1329234820edf || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <78d6f9a9eb2a5da6fcbd76d6191d24b0dcc321be || >=016c4d92cd16f569c6485ae62b076c1a4b779536 <3ef938c3503563bfc2ac15083557f880d29c2e64 | 618d5612ecb7bfc1c85342daafeb2b47e29e77a3, 556d446068f90981e5d71ca686bdaccdd545d491, 0a8f806ea6b5dd64b3d1f05ff774817d5f7ddbd1, 0708fd6bd8161871bfbadced2ca4319b84ab44fe, 7085895c59e4057ffae17f58990ccb630087d0d2, 93224deb50a8d20df3884f3672ce9f982129aa50, 320ac1af4c0bdb92c864dc9250d1329234820edf, 78d6f9a9eb2a5da6fcbd76d6191d24b0dcc321be, 3ef938c3503563bfc2ac15083557f880d29c2e64 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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/[email protected]/>) would probably be making the impact of this a lot worse.
Quoted source text, attributed separately from HOL analysis.