[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120941-CVE-2022-50657-6582@gregkh>
Date: Tue, 9 Dec 2025 10:30:42 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50657: riscv: mm: add missing memcpy in kasan_init
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
riscv: mm: add missing memcpy in kasan_init
Hi Atish,
It seems that the panic is due to the missing memcpy during kasan_init.
Could you please check whether this patch is helpful?
When doing kasan_populate, the new allocated base_pud/base_p4d should
contain kasan_early_shadow_{pud, p4d}'s content. Add the missing memcpy
to avoid page fault when read/write kasan shadow region.
Tested on:
- qemu with sv57 and CONFIG_KASAN on.
- qemu with sv48 and CONFIG_KASAN on.
The Linux kernel CVE team has assigned CVE-2022-50657 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit 8fbdccd2b17335e1881a23865e98c63fcc345938 and fixed in 6.0.7 with commit ff0f6becf3a6f817838b6f80a2c9cca43dce0576
Issue introduced in 5.18 with commit 8fbdccd2b17335e1881a23865e98c63fcc345938 and fixed in 6.1 with commit 9f2ac64d6ca60db99132e08628ac2899f956a0ec
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-50657
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/mm/kasan_init.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/ff0f6becf3a6f817838b6f80a2c9cca43dce0576
https://git.kernel.org/stable/c/9f2ac64d6ca60db99132e08628ac2899f956a0ec
Powered by blists - more mailing lists