CVE-2025-38435: riscv: vector: Fix context save/restore with xtheadvector
In the Linux kernel, the following vulnerability has been resolved:
riscv: vector: Fix context save/restore with xtheadvector
Previously only v0-v7 were correctly saved/restored,
and the context of v8-v31 are damanged.
Correctly save/restore v8-v31 to avoid breaking userspace.
Security readout for executives and security teams
Plain-English summary
Affected Linux kernels on certain RISC-V systems can mishandle processor state when switching between tasks. This may corrupt application data and, according to the 7.8 CVSS assessment, could affect confidentiality, integrity, and availability. Exploitation requires local, low-privileged access; remotely exposed services are not directly identified as an attack path.
Executive priority
Prioritize systems running untrusted or multi-tenant workloads on affected RISC-V hardware. Other environments should remediate through normal high-severity patching, after confirming applicability. The local-access requirement reduces immediate internet-facing risk, but possible process-state corruption warrants timely action.
Technical view
With the xtheadvector extension, Linux correctly saved and restored only vector registers v0-v7. Registers v8-v31 could be corrupted during context restoration, breaking userspace and potentially exposing or altering process state. The supplied references identify two Linux stable fixes.
Likely exposure
Exposure appears limited to RISC-V systems using xtheadvector and an affected kernel. The bundle lists Linux 6.14, 6.15.5, and 6.16 as affected, but also contains an ambiguous “0” version entry. Distribution package ranges and backports must therefore be confirmed with vendors.
Exploitation context
The CVSS vector indicates a local attacker needs low privileges, with low complexity and no user interaction. The supplied material provides no evidence of active exploitation, and the CVE is not marked as included in CISA KEV. No remote attack path is documented.
Researcher notes
The defect concerns context preservation rather than memory bounds: v0-v7 were handled correctly, while v8-v31 were damaged. The source bundle does not establish exploitability beyond the CVSS assessment, provide proof-of-concept evidence, or clearly map every fixed release. Validate vendor backports against the referenced commits.
Mitigation direction
Inventory RISC-V systems and determine whether xtheadvector support is active.
Consult distribution guidance to map the referenced fixes to exact kernel packages.
Install a vendor kernel update containing the applicable stable fix.
Until updated, restrict untrusted local users and workloads on exposed systems.
Validation and detection
Confirm each system’s architecture, active kernel version, and xtheadvector usage.
Verify the installed kernel includes the referenced fix or an equivalent vendor backport.
After updating, confirm the corrected kernel is active following reboot.
Review vector-intensive workloads for unexplained failures or data corruption.
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-2025-38435 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.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.