CVE-2025-33235VulnerabilityPublished 16 Dec 2025

CVE-2025-33235: NVIDIA Resiliency Extension · Race Condition

Affects NVIDIA Resiliency ExtensionSource CVE Database V5

Not known to be exploited · CVSS 7.8 High : upgrade to 0.5.0 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.5.0

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade NVIDIA Resiliency Extension to 0.5.0.

Affected software

Product	Affected	Fixed in
NVIDIA Resiliency Extension	Affected <0.5.0 =0.4.1	Fixed in 0.5.0

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately restrict local access to systems running vulnerable versions of NVIDIA Resiliency Extension, enforcing strict role-based access controls and monitoring for unusual local activity. 2) Employ Linux security modules (e.g., SELinux, AppArmor) to limit process capabilities and isolate the checkpointing component. 3) Monitor system logs and audit trails for race condition exploitation indicators such as unexpected process behavior or checkpoint failures. 4) Prepare for rapid deployment of patches once NVIDIA releases fixed versions beyond 0.5.0. 5) Conduct thorough code reviews and testing in environments using the extension to detect synchronization issues. 6) Educate system administrators about the risks of local privilege escalation and enforce multi-factor authentication to reduce insider threat risks. 7) Consider temporary disabling or limiting use of the checkpointing feature if feasible until patches are available.

Description

CVE-2025-33235 is a high-severity race condition vulnerability in the NVIDIA Resiliency Extension for Linux, specifically in its checkpointing core. This flaw allows an attacker with limited privileges and local access to exploit improper synchronization of shared resources, potentially leading to information disclosure, data tampering, denial of service, or privilege escalation. The vulnerability affects versions prior to 0.5.0 and 0.4.1. Exploitation does not require user interaction but does require local access with some privileges. No known exploits are currently in the wild.

Impact

For European organizations, especially those relying on NVIDIA Resiliency Extension in Linux environments for critical infrastructure, cloud services, or high-availability systems, this vulnerability poses a substantial risk. Exploitation could lead to unauthorized disclosure of sensitive information, corruption or tampering of critical data, denial of service conditions that disrupt business operations, and privilege escalation that could facilitate further compromise. Industries such as finance, telecommunications, manufacturing, and government sectors that deploy NVIDIA's Linux-based resiliency solutions are particularly at risk. The local attack vector limits remote exploitation but insider threats or compromised accounts could leverage this vulnerability. The impact on confidentiality, integrity, and availability could result in regulatory non-compliance, financial losses, and reputational damage within the European market.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Dec 2025, 18:39 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats