CVE-2022-49001: riscv: fix race when vmap stack overflow
In the Linux kernel, the following vulnerability has been resolved:
riscv: fix race when vmap stack overflow
Currently, when detecting vmap stack overflow, riscv firstly switches
to the so called shadow stack, then use this shadow stack to call the
get_overflow_stack() to get the overflow stack. However, there's
a race here if two or more harts use the same shadow stack at the same
time.
To solve this race, we introduce spin_shadow_stack atomic var, which
will be swap between its own address and 0 in atomic way, when the
var is set, it means the shadow_stack is being used; when the var
is cleared, it means the shadow_stack isn't being used.
[Palmer: Add AQ to the swap, and also some comments.]
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel issue limited to RISC-V handling of vmap stack overflow. Two or more RISC-V harts can race while using the same shadow stack during overflow handling. The source bundle does not state business impact, CVSS severity, exploitability, or active exploitation.
Executive priority
Treat this as a targeted kernel maintenance item for RISC-V Linux environments. Urgency is constrained by missing severity and no cited exploitation, but kernel races can have reliability or security impact. Patch through normal vendor-supported channels, faster for production RISC-V systems.
Technical view
The vulnerable path switches to a shadow stack before calling get_overflow_stack(). If multiple harts enter this overflow path concurrently, they can share the same shadow stack. The resolved change introduces an atomic spin_shadow_stack variable to serialize shadow stack use, swapping between its own address and zero.
Likely exposure
Exposure appears limited to Linux systems running affected RISC-V kernels with vmap stack overflow handling. The bundle lists Linux kernel versions including 5.14, 5.15.82, 6.0.12, and 6.1, but distro-specific affected ranges are not provided.
Exploitation context
CISA KEV status is false, and the provided sources do not report public exploitation. The condition is a kernel race involving concurrent harts entering an overflow path. The bundle does not state whether an unprivileged local user can trigger it.
Researcher notes
Evidence is strongest for root cause and fix mechanics, not impact. The CVE text describes a race in shadow stack reuse during vmap stack overflow handling and references stable kernel commits. No CWE, CVSS, trigger conditions, or privilege boundary are provided.
Mitigation direction
Check Linux vendor or distribution guidance for CVE-2022-49001.
Apply kernel updates containing the referenced stable fixes.
Prioritize RISC-V systems over non-RISC-V Linux assets.
Schedule maintenance windows for kernel replacement and reboot.
Avoid claiming remediation until the running kernel is verified.
Validation and detection
Inventory Linux assets by CPU architecture and kernel version.
Confirm whether any RISC-V systems run affected kernel builds.
Map installed kernel packages to vendor advisories or stable commits.
After updating, verify the running kernel changed.
Review kernel changelogs for the CVE or referenced commits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49001 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.