CVE-2025-23359

Public Exploit

Description

NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default configuration, where a crafted container image could gain access to the host file system. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Remediation

Workaround:

  • This vulnerability does not impact use cases where CDI is used. The fix for this vulnerability changes the default behavior of the NVIDIA Container Toolkit. By default the NVIDIA CUDA compatibility libraries from /usr/local/cuda/compat in the container are no longer mounted to the default library path in the container being run. This may affect certain applications that depend on this behavior. A feature flag, allow-cuda-compat-libs-from-container was included in the NVIDIA Container Toolkit to allow users to opt-in to the previous behavior if required. Warning: Opting-in to the previous behavior will remove protection against this vulnerability and is not recommended. To set the feature flag ensure that the NVIDIA Container Toolkit config file at /etc/nvidia-container-runtime/config.toml includes: [features]   allow-cuda-compat-libs-from-container = true  Setting the value above to false or removing the config file entry will disable the feature. In the case of the NVIDIA GPU Operator the feature flag can be set by including the following in the NVIDIA GPU Operator helm install command: --set "toolkit.env[0].name=NVIDIA_CONTAINER_TOOLKIT_OPT_IN_FEATURES" --set "toolkit.env[0].value=allow-cuda-compat-libs-from-container"   For users who know that their application needs CUDA Forward Compatibility the following workaround can be used: Setting the LD_LIBRARY_PATH environment variable to include /usr/local/cuda/compat This may cause portability issues for some containers when running across multiple driver versions – especially when these are more recent than the compatibility libraries in the container.

Category

8.3
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.15%
Affected: NVIDIA Container Toolkit
Affected: NVIDIA GPU Operator
Published at:
Updated at:

References

Link Tags
https://nvidia.custhelp.com/app/answers/detail/a_id/5616
https://thehackernews.com/2025/04/incomplete-patch-in-nvidia-toolkit.html

Frequently Asked Questions

What is the severity of CVE-2025-23359?
CVE-2025-23359 has been scored as a high severity vulnerability.
How to fix CVE-2025-23359?
As a workaround for remediating CVE-2025-23359: This vulnerability does not impact use cases where CDI is used. The fix for this vulnerability changes the default behavior of the NVIDIA Container Toolkit. By default the NVIDIA CUDA compatibility libraries from /usr/local/cuda/compat in the container are no longer mounted to the default library path in the container being run. This may affect certain applications that depend on this behavior. A feature flag, allow-cuda-compat-libs-from-container was included in the NVIDIA Container Toolkit to allow users to opt-in to the previous behavior if required. Warning: Opting-in to the previous behavior will remove protection against this vulnerability and is not recommended. To set the feature flag ensure that the NVIDIA Container Toolkit config file at /etc/nvidia-container-runtime/config.toml includes: [features]   allow-cuda-compat-libs-from-container = true  Setting the value above to false or removing the config file entry will disable the feature. In the case of the NVIDIA GPU Operator the feature flag can be set by including the following in the NVIDIA GPU Operator helm install command: --set "toolkit.env[0].name=NVIDIA_CONTAINER_TOOLKIT_OPT_IN_FEATURES" --set "toolkit.env[0].value=allow-cuda-compat-libs-from-container"   For users who know that their application needs CUDA Forward Compatibility the following workaround can be used: Setting the LD_LIBRARY_PATH environment variable to include /usr/local/cuda/compat This may cause portability issues for some containers when running across multiple driver versions – especially when these are more recent than the compatibility libraries in the container.
Is CVE-2025-23359 being actively exploited in the wild?
It is possible that CVE-2025-23359 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-23359?
CVE-2025-23359 affects NVIDIA Container Toolkit, NVIDIA GPU Operator.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.