GHSA-JCQW-583M-JHJV
Vulnerability from github – Published: 2025-12-09 18:30 – Updated: 2025-12-09 18:30
VLAI?
Details
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.
{
"affected": [],
"aliases": [
"CVE-2022-50657"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-09T16:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: mm: add missing memcpy in kasan_init\n\nHi Atish,\n\nIt seems that the panic is due to the missing memcpy during kasan_init.\nCould you please check whether this patch is helpful?\n\nWhen doing kasan_populate, the new allocated base_pud/base_p4d should\ncontain kasan_early_shadow_{pud, p4d}\u0027s content. Add the missing memcpy\nto avoid page fault when read/write kasan shadow region.\n\nTested on:\n - qemu with sv57 and CONFIG_KASAN on.\n - qemu with sv48 and CONFIG_KASAN on.",
"id": "GHSA-jcqw-583m-jhjv",
"modified": "2025-12-09T18:30:30Z",
"published": "2025-12-09T18:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50657"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9f2ac64d6ca60db99132e08628ac2899f956a0ec"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ff0f6becf3a6f817838b6f80a2c9cca43dce0576"
}
],
"schema_version": "1.4.0",
"severity": []
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…