Security readout for executives and security teams
Plain-English summary
OpenSBI 1.3 can be crashed by a crafted request to its performance-monitoring interface, causing denial of service. The reported impact is loss of availability, not data theft or modification. Business risk depends on whether untrusted software can invoke the affected SBI function in deployed RISC-V systems.
Executive priority
Prioritize exposure discovery immediately and remediation promptly for availability-critical systems. The high CVSS score reflects an apparently simple denial-of-service condition, but urgency should be adjusted after confirming OpenSBI 1.3 usage and attacker reachability. There is no supplied evidence of active exploitation or data compromise.
Technical view
CVE-2025-63913 is a CWE-400 resource-consumption issue in OpenSBI 1.3. Crafted input to SBI function 2, described as the PMU extension’s counter-matching and configuration function, can trigger denial of service. CVSS 3.1 rates it 7.5: low-complexity, unauthenticated exploitation with high availability impact and no reported confidentiality or integrity impact.
Likely exposure
Exposure is limited to systems using OpenSBI 1.3 where an attacker can submit crafted requests to the affected SBI PMU function. The supplied CVE metadata does not identify platforms, distributions, CPEs, or a confirmed remote delivery path, so organizations must establish reachability within their own RISC-V deployments.
Exploitation context
The supplied record links a public crash-focused repository, indicating technical reproduction information exists. However, the CVE is not listed as KEV, and the supplied sources do not establish active exploitation in the wild. Treat public technical details as increasing reproducibility, without equating them to confirmed operational attacks.
Researcher notes
The evidence is sparse: affected-product fields and CPEs are unspecified, despite the description naming OpenSBI 1.3. No corrected version or vendor mitigation is identified in the supplied bundle. Researchers should distinguish the CVSS network vector from demonstrated deployment reachability and avoid inferring broader version impact.
Mitigation direction
- Inventory RISC-V systems and firmware using OpenSBI 1.3.
- Check current OpenSBI guidance for a corrected release or approved mitigation.
- Restrict untrusted software from invoking SBI PMU functions where operationally feasible.
- Prioritize availability-sensitive and multi-tenant systems for remediation planning.
- Monitor affected systems for unexplained firmware crashes or repeated service resets.
Validation and detection
- Confirm the deployed OpenSBI version from trusted build or firmware records.
- Identify whether untrusted workloads can reach the SBI PMU extension.
- Review crash logs for failures associated with PMU counter configuration.
- Verify any vendor-recommended update in a controlled environment.
- Confirm availability monitoring detects firmware crashes and service recovery.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-63913 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/luojia65/opensbi-pmu2-crashCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.