Andres Riancho

NVIDIA Container Toolkit and NVIDIA GPU Operator are affected by a Time-of-Check Time-of-Use (TOCTOU) vulnerability. This flaw can allow a crafted container image to gain access to the host file system, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. A bypass was discovered for a previously patched security flaw, reflagged as CVE-2025-23359. The vulnerability exists due to errors in synchronization when using a shared resource, creating a race condition.

The issue is related to an improper isolation vulnerability where a specially crafted container image could lead to modification of a host binary. A successful exploit may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The "GET /api/v1/status/{job id}" and "POST /api/v1/search" API endpoints are mentioned, with the `job id` variable and `Content-Type` being relevant. No information is provided about the estimated number of potentially affected devices or real-world incidents.

The NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to untrusted code obtaining read and write access to host devices. This issue is present only when the NVIDIA Container Toolkit is configured in a nondefault way. A successful exploit may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

The NVIDIA Container Toolkit contains an improper isolation vulnerability. A specially crafted container image could lead to untrusted code running in the host’s network namespace. This issue is present only when the NVIDIA Container Toolkit is configured in a nondefault way. A successful exploit may lead to denial of service and escalation of privileges.

The issue is related to errors in processing symbolic links, which can be exploited by a remote attacker to impact data integrity. A specially crafted container image can lead to the creation of unauthorized files on the host, although the name and location of these files cannot be controlled by the attacker. This might result in data tampering.

The issue is related to the default mode of operation in NVIDIA Container Toolkit, allowing a specially crafted container image to create empty files on the host file system. This vulnerability does not impact use cases where CDI is used. A successful exploit may lead to data tampering. The vulnerability is also associated with a null pointer dereference due to concurrent access to a resource, potentially allowing a remote attacker to modify arbitrary data by using a specially crafted container image.

The issue allows remote attackers to cause a denial of service, resulting in a page fault, by sending a malformed packet, which can force the device into layer 2 fallback.