CVE-2026-29643
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-29643 is a high-severity Improper Check or Handling of Exceptional Conditions (CWE-703) vulnerability in Riscv (inferred from references). Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-29643 is an improper exceptional-condition handling flaw (CWE-703) in the CSR subsystem, known as NewCSR, of XiangShan, an open-source high-performance RISC-V processor. The vulnerability affects commit edb1dfaf7d290ae99724594507dc46c2c2125384 dated 2024-11-28. In affected versions, specific sequences of CSR operations targeting non-existent or custom CSR addresses trigger an illegal-instruction exception but fail to reliably transfer control to the configured trap handler (mtvec), resulting in control-flow disruption that can leave the core in a hung or unrecoverable state.
A local attacker with the ability to execute code on the processor (AV:L/PR:L) can exploit this issue with low complexity and no user interaction required. Successful exploitation causes a denial of service by disrupting core operation and may lead to inconsistent architectural state, with high impacts on integrity (I:H) and availability (A:H) but no confidentiality impact (C:N). The CVSS v3.1 base score is 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H).
The issue is documented in XiangShan GitHub issue #3959, with a patch available in pull request #3966. Related RISC-V specifications are referenced in the privileged ISA documentation for machine mode (mtvec) and private CSRs.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23957
Vulnerability Data
XiangShan (Open-source high-performance RISC-V processor) commit edb1dfaf7d290ae99724594507dc46c2c2125384 (2024-11-28) contains an improper exceptional-condition handling flaw in its CSR subsystem (NewCSR). On affected versions, certain sequences of CSR operations targeting non-existent/custom CSR addresses may trigger an illegal-instruction exception but fail to reliably…
more
transfer control to the configured trap handler (mtvec), causing control-flow disruption and potentially leaving the core in a hung or unrecoverable state. This can be exploited by a local attacker able to execute code on the processor to cause a denial of service and potentially inconsistent architectural state.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces failure to a known state while preserving required properties, limiting impact of unhandled exceptions.
Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled exceptional conditions.
Requires application of security engineering principles that include robust exception and error handling during design.
Requires generation of safe, actionable error messages that directly addresses proper handling of exceptional conditions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly require anticipating and correctly handling exceptional conditions during design and coding.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Reporting of unhandled errors or exceptional conditions surfaces latent failure paths so they can be corrected before exploitation.