[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121636-CVE-2025-40353-fb93@gregkh>
Date: Tue, 16 Dec 2025 14:30:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40353: arm64: mte: Do not warn if the page is already tagged in copy_highpage()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
arm64: mte: Do not warn if the page is already tagged in copy_highpage()
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 ("mm: migrate:
support poisoned recover from migrate folio"), 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.
Replace the WARN_ON_ONCE(page already tagged) in the arm64
copy_highpage() with a comment.
The Linux kernel CVE team has assigned CVE-2025-40353 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.56 with commit 5ff5765a1fc526f07d3bbaedb061d970eb13bcf4
Fixed in 6.17.6 with commit 0bbf3fc6e9211fce9889fe8efbb89c220504d617
Fixed in 6.18 with commit b98c94eed4a975e0c80b7e90a649a46967376f58
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-40353
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/arm64/mm/copypage.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/5ff5765a1fc526f07d3bbaedb061d970eb13bcf4
https://git.kernel.org/stable/c/0bbf3fc6e9211fce9889fe8efbb89c220504d617
https://git.kernel.org/stable/c/b98c94eed4a975e0c80b7e90a649a46967376f58
Powered by blists - more mailing lists