Security readout for executives and security teams
Plain-English summary
This CVE describes a denial-of-service risk in OneFlow v0.9.0. If an attacker can influence a GPU device index passed to flow.cuda.get_device_properties(), an invalid or negative value may crash or disrupt availability. The source bundle does not identify data theft or code execution.
Executive priority
Prioritize if OneFlow v0.9.0 supports customer-facing or shared GPU workloads. Availability loss is the reported impact, not confidentiality or integrity compromise.
Technical view
The reported flaw is improper GPU device-ID validation in OneFlow v0.9.0, mapped to CWE-400. The CVSS 3.1 score is 7.5 with availability impact only. The affected metadata is incomplete, but the description and references identify OneFlow and the get_device_properties CUDA path.
Likely exposure
Exposure appears limited to deployments using OneFlow v0.9.0 with CUDA/GPU functionality where untrusted input can reach GPU device-index handling.
Exploitation context
The bundle marks KEV as false and provides no evidence of active exploitation. Public references include the OneFlow repository and a GitHub issue, but no confirmed patch details are included.
Researcher notes
Affected vendor/product fields are listed as n/a, creating attribution uncertainty. The description identifies OneFlow v0.9.0, but the bundle does not provide fixed versions, vendor advisory details, or active exploitation evidence.
Mitigation direction
- Check OneFlow vendor guidance and issue 10661 for fixed release information.
- Restrict untrusted access to services calling OneFlow CUDA device-property APIs.
- Validate GPU device indices before calling OneFlow APIs.
- Block negative or out-of-range device IDs at application boundaries.
- Monitor affected services for crashes tied to CUDA device-property lookups.
Validation and detection
- Inventory systems running OneFlow and confirm exact versions.
- Identify code paths calling flow.cuda.get_device_properties().
- Check whether user-controlled input can influence device index values.
- Confirm wrapper validation rejects invalid GPU device IDs.
- Review service logs for crashes around CUDA device-property requests.
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-65891 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/Daisy2angCVE reference, mitre
- https://github.com/Oneflow-Inc/oneflowCVE reference, mitre
- https://github.com/Oneflow-Inc/oneflow/issues/10661CVE 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.