[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025052045-CVE-2025-37966-8d4c@gregkh>
Date: Tue, 20 May 2025 18:45:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-37966: riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
When userspace does PR_SET_TAGGED_ADDR_CTRL, but Supm extension is not
available, the kernel crashes:
Oops - illegal instruction [#1]
[snip]
epc : set_tagged_addr_ctrl+0x112/0x15a
ra : set_tagged_addr_ctrl+0x74/0x15a
epc : ffffffff80011ace ra : ffffffff80011a30 sp : ffffffc60039be10
[snip]
status: 0000000200000120 badaddr: 0000000010a79073 cause: 0000000000000002
set_tagged_addr_ctrl+0x112/0x15a
__riscv_sys_prctl+0x352/0x73c
do_trap_ecall_u+0x17c/0x20c
andle_exception+0x150/0x15c
Fix it by checking if Supm is available.
The Linux kernel CVE team has assigned CVE-2025-37966 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 09d6775f503b393d0457c7126aa43208e1724004 and fixed in 6.14.7 with commit 4b595a2f5656cd45d534ed2160c94f7662adefe5
Issue introduced in 6.13 with commit 09d6775f503b393d0457c7126aa43208e1724004 and fixed in 6.15-rc6 with commit ae08d55807c099357c047dba17624b09414635dd
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-37966
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/riscv/kernel/process.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/4b595a2f5656cd45d534ed2160c94f7662adefe5
https://git.kernel.org/stable/c/ae08d55807c099357c047dba17624b09414635dd
Powered by blists - more mailing lists