CVE-2025-65890 Oneflow Inc. CVE debrief

Who should care

Users of OneFlow v0.9.0, particularly those in operator, platform, vulnerability-management, and security teams, should be aware of this vulnerability and take necessary precautions to prevent exploitation. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Technical summary

The vulnerability is caused by a device-ID validation flaw in OneFlow v0.9.0, which allows attackers to cause a Denial of Service (DoS) by calling flow.cuda.synchronize() with an invalid or out-of-range GPU device index. The vulnerability has a CVSS vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. This issue can be particularly problematic in environments where the GPU device index is not properly validated, allowing for potential exploitation. Users should be cautious and ensure that they are using a version of OneFlow that has addressed this vulnerability.

Defensive priority

High priority should be given to patching or mitigating this vulnerability, as it can be exploited to cause a Denial of Service (DoS). Defenders should review compensating controls for exposed systems while remediation is scheduled and verified, and track exceptions, retest remediated assets, and close the item only after evidence is documented.

Recommended defensive actions

• Patch OneFlow to the latest version
• Restrict access to the vulnerable component
• Monitor for suspicious activity
• Implement compensating controls
• Verify inventory for affected systems

Evidence notes

The CVE record and NVD detail provide information on the vulnerability, including its CVSS score and vector. The source item URL provides additional information on the vulnerability. However, the details provided are limited, and further verification is necessary to fully understand the scope and impact of the vulnerability. Defenders should verify the affected scope, severity, and vendor guidance to ensure proper mitigation.

Official resources