<?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>Tue, 29 Sep 2026 15:33:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63875 — arm64: tlb: Flush walk cache when unsharing PMD tables</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63875</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;arm64: tlb: Flush walk cache when unsharing PMD tables&lt;/p&gt;
&lt;p&gt;When huge_pmd_unshare() is called to unshare a PMD table, the
tlb_unshare_pmd_ptdesc() function sets tlb-&amp;gt;unshared_tables=true
but the aarch64 tlb_flush() only checked tlb-&amp;gt;freed_tables to
determine whether to use TLBF_NONE (vae1is, invalidates walk
cache) or TLBF_NOWALKCACHE (vale1is, leaf-only).&lt;/p&gt;
&lt;p&gt;This caused the stale PMD page table entry to remain in the walk cache
after unshare, potentially leading to incorrect page table walks.&lt;/p&gt;
&lt;p&gt;Fix by including unshared_tables in the check, so that when
unsharing tables, TLBF_NONE is used and the walk cache is properly
invalidated.&lt;/p&gt;
&lt;p&gt;Here is the detailed distinction between vae1is and vale1is:&lt;/p&gt;
&lt;p&gt;| Instruction Combination  | Actual Invalidation Scope                         |
| ------------------------ | --------------------------------------------------|
| `VAE1IS`  + TTL=`0`      | All entries at all levels (full invalidation)     |
| `VAE1IS`  + TTL=`2` (L2) | Non-leaf at Level 0/1 + leaf at Level 2           |
| `VALE1IS` + TTL=`0`      | Leaf entries at all levels (non-leaf not cleared) |
| `VALE1IS` + TTL=`2` (L2) | Leaf entry at Level 2 only                        |&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;arm64: tlb: Flush walk cache when unsharing PMD tables&lt;/p&gt;
&lt;p&gt;When huge_pmd_unshare() is called to unshare a PMD table, the
tlb_unshare_pmd_ptdesc() function sets tlb-&amp;gt;unshared_tables=true
but the aarch64 tlb_flush() only checked tlb-&amp;gt;freed_tables to
determine whether to use TLBF_NONE (vae1is, invalidates walk
cache) or TLBF_NOWALKCACHE (vale1is, leaf-only).&lt;/p&gt;
&lt;p&gt;This caused the stale PMD page table entry to remain in the walk cache
after unshare, potentially leading to incorrect page table walks.&lt;/p&gt;
&lt;p&gt;Fix by including unshared_tables in the check, so that when
unsharing tables, TLBF_NONE is used and the walk cache is properly
invalidated.&lt;/p&gt;
&lt;p&gt;Here is the detailed distinction between vae1is and vale1is:&lt;/p&gt;
&lt;p&gt;| Instruction Combination  | Actual Invalidation Scope                         |
| ------------------------ | --------------------------------------------------|
| `VAE1IS`  + TTL=`0`      | All entries at all levels (full invalidation)     |
| `VAE1IS`  + TTL=`2` (L2) | Non-leaf at Level 0/1 + leaf at Level 2           |
| `VALE1IS` + TTL=`0`      | Leaf entries at all levels (non-leaf not cleared) |
| `VALE1IS` + TTL=`2` (L2) | Leaf entry at Level 2 only                        |&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63875</guid>
    </item>
  </channel>
</rss>
