# CVE-2022-50657: linux: In the Linux kernel, the following vulnerability has been resolved:  riscv: mm: add missing memcpy in kasan_init  Hi...

CVE-2022-50657 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50657, released December 9, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2022-50657
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0023
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Dec 9, 2025

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.0.7-1 | [DEBIAN-CVE-2022-50657](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50657.md) | Dec 9, 2025 |
| Linux | linux Debian 13.5 (trixie) | 6.0.7-1 | [DEBIAN-CVE-2022-50657](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50657.md) | Dec 9, 2025 |
| Linux | linux Debian 14 | 6.0.7-1 | [DEBIAN-CVE-2022-50657](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50657.md) | Dec 9, 2025 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.