<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 08:37:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22045 — x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-22045</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;collapse_pte_mapped_thp
      pmdp_collapse_flush
        flush_tlb_range&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Currently, X86 only uses this information for the following two purposes,
which I think means the issue doesn&amp;#39;t have much impact:&lt;/p&gt;
&lt;p&gt;- In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be
   IPI&amp;#39;d to avoid issues with speculative page table walks.
 - In Hyper-V TLB paravirtualization, again for lazy TLB stuff.&lt;/p&gt;
&lt;p&gt;The patch &amp;#34;x86/mm: only invalidate final translations with INVLPGB&amp;#34; which
is currently under review (see
&amp;lt;https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/&amp;gt;)
would probably be making the impact of this a lot worse.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;collapse_pte_mapped_thp
      pmdp_collapse_flush
        flush_tlb_range&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Currently, X86 only uses this information for the following two purposes,
which I think means the issue doesn&amp;#39;t have much impact:&lt;/p&gt;
&lt;p&gt;- In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be
   IPI&amp;#39;d to avoid issues with speculative page table walks.
 - In Hyper-V TLB paravirtualization, again for lazy TLB stuff.&lt;/p&gt;
&lt;p&gt;The patch &amp;#34;x86/mm: only invalidate final translations with INVLPGB&amp;#34; which
is currently under review (see
&amp;lt;https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/&amp;gt;)
would probably be making the impact of this a lot worse.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-22045</guid>
    </item>
  </channel>
</rss>
