[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061848-CVE-2022-50225-bbfc@gregkh>
Date: Wed, 18 Jun 2025 13:04:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50225: riscv:uprobe fix SR_SPIE set/clear handling
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
riscv:uprobe fix SR_SPIE set/clear handling
In riscv the process of uprobe going to clear spie before exec
the origin insn,and set spie after that.But When access the page
which origin insn has been placed a page fault may happen and
irq was disabled in arch_uprobe_pre_xol function,It cause a WARN
as follows.
There is no need to clear/set spie in arch_uprobe_pre/post/abort_xol.
We can just remove it.
[ 31.684157] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1488
[ 31.684677] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 76, name: work
[ 31.684929] preempt_count: 0, expected: 0
[ 31.685969] CPU: 2 PID: 76 Comm: work Tainted: G
[ 31.686542] Hardware name: riscv-virtio,qemu (DT)
[ 31.686797] Call Trace:
[ 31.687053] [<ffffffff80006442>] dump_backtrace+0x30/0x38
[ 31.687699] [<ffffffff80812118>] show_stack+0x40/0x4c
[ 31.688141] [<ffffffff8081817a>] dump_stack_lvl+0x44/0x5c
[ 31.688396] [<ffffffff808181aa>] dump_stack+0x18/0x20
[ 31.688653] [<ffffffff8003e454>] __might_resched+0x114/0x122
[ 31.688948] [<ffffffff8003e4b2>] __might_sleep+0x50/0x7a
[ 31.689435] [<ffffffff80822676>] down_read+0x30/0x130
[ 31.689728] [<ffffffff8000b650>] do_page_fault+0x166/x446
[ 31.689997] [<ffffffff80003c0c>] ret_from_exception+0x0/0xc
The Linux kernel CVE team has assigned CVE-2022-50225 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 74784081aac8a0f3636965fc230e2d3b7cc123c6 and fixed in 5.15.61 with commit c71e000db8536d27ec410abb3e314896a78b4f19
Issue introduced in 5.12 with commit 74784081aac8a0f3636965fc230e2d3b7cc123c6 and fixed in 5.18.18 with commit 3811d51778900064d27d8c9a98f73410fb3b471d
Issue introduced in 5.12 with commit 74784081aac8a0f3636965fc230e2d3b7cc123c6 and fixed in 5.19.2 with commit 73fc099eaefd9a92c83b6c07dad066411fd5a192
Issue introduced in 5.12 with commit 74784081aac8a0f3636965fc230e2d3b7cc123c6 and fixed in 6.0 with commit 3dbe5829408bc1586f75b4667ef60e5aab0209c7
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-2022-50225
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/probes/uprobes.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/c71e000db8536d27ec410abb3e314896a78b4f19
https://git.kernel.org/stable/c/3811d51778900064d27d8c9a98f73410fb3b471d
https://git.kernel.org/stable/c/73fc099eaefd9a92c83b6c07dad066411fd5a192
https://git.kernel.org/stable/c/3dbe5829408bc1586f75b4667ef60e5aab0209c7
Powered by blists - more mailing lists