[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122413-CVE-2025-68737-596a@gregkh>
Date: Wed, 24 Dec 2025 13:10:13 +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-68737: arm64/pageattr: Propagate return value from __change_memory_common
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
arm64/pageattr: Propagate return value from __change_memory_common
The rodata=on security measure requires that any code path which does
vmalloc -> set_memory_ro/set_memory_rox must protect the linear map alias
too. Therefore, if such a call fails, we must abort set_memory_* and caller
must take appropriate action; currently we are suppressing the error, and
there is a real chance of such an error arising post commit a166563e7ec3
("arm64: mm: support large block mapping when rodata=full"). Therefore,
propagate any error to the caller.
The Linux kernel CVE team has assigned CVE-2025-68737 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit a166563e7ec375b38a0fd3a58f7b77e50a6bc6a8 and fixed in 6.18.2 with commit 3e2fc1e57a5361633a4bf4222640c6bfe41ff8ea
Issue introduced in 6.18 with commit a166563e7ec375b38a0fd3a58f7b77e50a6bc6a8 and fixed in 6.19-rc1 with commit e5efd56fa157d2e7d789949d1d64eccbac18a897
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-68737
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/pageattr.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/3e2fc1e57a5361633a4bf4222640c6bfe41ff8ea
https://git.kernel.org/stable/c/e5efd56fa157d2e7d789949d1d64eccbac18a897
Powered by blists - more mailing lists