[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021859-CVE-2025-71228-d43d@gregkh>
Date: Wed, 18 Feb 2026 15:22:03 +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-71228: LoongArch: Set correct protection_map[] for VM_NONE/VM_SHARED
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Set correct protection_map[] for VM_NONE/VM_SHARED
For 32BIT platform _PAGE_PROTNONE is 0, so set a VMA to be VM_NONE or
VM_SHARED will make pages non-present, then cause Oops with kernel page
fault.
Fix it by set correct protection_map[] for VM_NONE/VM_SHARED, replacing
_PAGE_PROTNONE with _PAGE_PRESENT.
The Linux kernel CVE team has assigned CVE-2025-71228 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.163 with commit 046303283d02c9732a778ccdeea433a899c78cbd
Fixed in 6.6.124 with commit 5fbdf95d2575ec53fd4a5c18e789b4d54a0281fe
Fixed in 6.12.70 with commit 380d7c1af4bd3e797692f5410ab374a98e766cd4
Fixed in 6.18.10 with commit 9531210f348aa78e260a9e5b0d1a6f7e7aa329e6
Fixed in 6.19 with commit d5be446948b379f1d1a8e7bc6656d13f44c5c7b1
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-71228
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/loongarch/mm/cache.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/046303283d02c9732a778ccdeea433a899c78cbd
https://git.kernel.org/stable/c/5fbdf95d2575ec53fd4a5c18e789b4d54a0281fe
https://git.kernel.org/stable/c/380d7c1af4bd3e797692f5410ab374a98e766cd4
https://git.kernel.org/stable/c/9531210f348aa78e260a9e5b0d1a6f7e7aa329e6
https://git.kernel.org/stable/c/d5be446948b379f1d1a8e7bc6656d13f44c5c7b1
Powered by blists - more mailing lists