CVE-2025-39815: RISC-V: KVM: fix stack overrun when loading vlenb
In the Linux kernel, the following vulnerability has been resolved:
RISC-V: KVM: fix stack overrun when loading vlenb
The userspace load can put up to 2048 bits into an xlen bit stack
buffer. We want only xlen bits, so check the size beforehand.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux KVM on RISC-V can let a locally privileged user provide oversized vector-length data that overruns a kernel stack buffer. Successful exploitation could compromise confidentiality, integrity, and availability. Systems not using RISC-V KVM are unlikely to be exposed.
Executive priority
Treat as high priority where RISC-V KVM hosts process untrusted workloads or provide local access. Patch through normal emergency kernel maintenance after compatibility testing. Organizations without RISC-V KVM exposure should document non-applicability rather than initiate broad emergency action.
Technical view
The KVM RISC-V vlenb loading path accepted up to 2048 bits from userspace into an xlen-sized stack buffer. The resolved implementation checks the supplied size before loading it. The supplied CVSS 3.1 score is 7.8, requiring local access and low privileges, with no user interaction.
Likely exposure
Exposure is concentrated in affected Linux versions running KVM on RISC-V. The bundle identifies versions 6.8, 6.12.45, 6.16.5, and 6.17 as affected, but its version data is incomplete or ambiguous. Confirm distribution-specific status and backports with the kernel or operating-system vendor.
Exploitation context
The CVSS vector indicates local, low-privileged exploitation with low complexity and no user interaction. The source bundle does not establish remote exploitation or active exploitation in the wild, and the CVE is not listed as KEV.
Researcher notes
The defect is a stack overrun caused by a size mismatch between userspace-supplied vector data and an xlen-sized destination. No CWE is supplied. The record supports severe potential impact but does not establish reliable exploitation, observed attacks, or a particular post-corruption outcome. Affected-version boundaries require vendor confirmation.
Mitigation direction
Update to a vendor-supported kernel containing the referenced size-check fix.
Prioritize RISC-V hosts that run KVM or permit untrusted local users.
Consult distribution advisories for fixed package versions and backported patches.
Restrict unnecessary local and virtualization access until affected systems are updated.
Validation and detection
Inventory Linux systems using RISC-V architecture and KVM virtualization.
Compare installed kernel builds against vendor advisories and referenced stable commits.
Confirm the deployed kernel includes the vlenb input-size validation fix.
Retest KVM workloads after updating and monitor hosts for abnormal kernel failures.
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-39815 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.
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.