<?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>Wed, 30 Sep 2026 20:49:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40353 — arm64: mte: Do not warn if the page is already tagged in copy_highpage()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40353</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: mte: Do not warn if the page is already tagged in copy_highpage()&lt;/p&gt;
&lt;p&gt;The arm64 copy_highpage() assumes that the destination page is newly
allocated and not MTE-tagged (PG_mte_tagged unset) and warns
accordingly. However, following commit 060913999d7a (&amp;#34;mm: migrate:
support poisoned recover from migrate folio&amp;#34;), folio_mc_copy() is called
before __folio_migrate_mapping(). If the latter fails (-EAGAIN), the
copy will be done again to the same destination page. Since
copy_highpage() already set the PG_mte_tagged flag, this second copy
will warn.&lt;/p&gt;
&lt;p&gt;Replace the WARN_ON_ONCE(page already tagged) in the arm64
copy_highpage() with a comment.&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: mte: Do not warn if the page is already tagged in copy_highpage()&lt;/p&gt;
&lt;p&gt;The arm64 copy_highpage() assumes that the destination page is newly
allocated and not MTE-tagged (PG_mte_tagged unset) and warns
accordingly. However, following commit 060913999d7a (&amp;#34;mm: migrate:
support poisoned recover from migrate folio&amp;#34;), folio_mc_copy() is called
before __folio_migrate_mapping(). If the latter fails (-EAGAIN), the
copy will be done again to the same destination page. Since
copy_highpage() already set the PG_mte_tagged flag, this second copy
will warn.&lt;/p&gt;
&lt;p&gt;Replace the WARN_ON_ONCE(page already tagged) in the arm64
copy_highpage() with a comment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40353</guid>
    </item>
  </channel>
</rss>
