LiveActive security incident?Get immediate response
CVE Record

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

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.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux31da94c25aea835ceac00575a9fd206c5a833fed, 31da94c25aea835ceac00575a9fd206c5a833fed, 31da94c25aea835ceac00575a9fd206c5a833fedunaffected
LinuxLinux5.14, 0, 5.15.82, 6.0.12, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.