cve.bz

CVE-2025-23267 nvidia container toolkit: Link Following

8.5 highEPSS 0.9%Fix available

High (8.5) in nvidia container toolkit. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/NVIDIA/nvidia-container-toolkit 1.17.8.

On this page
NVIDIA Container Toolkit for all platforms contains a vulnerability in the update-ldcache hook, where an attacker could cause a link following by using a specially crafted container image. A successful exploit of this vulnerability might lead to data tampering and denial of service.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/NVIDIA/nvidia-container-toolkit (Go): fixed in 1.17.8
  • github.com/NVIDIA/k8s-device-plugin (Go): fixed in 0.17.3
  • github.com/NVIDIA/gpu-operator (Go): fixed in 25.3.2
  • github.com/NVIDIA/mig-parted (Go): fixed in 0.12.2
  • SUSE, openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-23267 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-23267?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-23267?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-23267 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
NVIDIA Container ToolkitNVIDIA Container Toolkit All versions up to and including 1.17.7
NVIDIA Container ToolkitNVIDIA GPU Operator All versions up to and including 25.3.0 (CDI

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-67jc-hmvg-q4c7Gogithub.com/NVIDIA/nvidia-container-toolkit<1.17.81.17.8
GHSA-67jc-hmvg-q4c7Gogithub.com/NVIDIA/k8s-device-plugin<0.17.30.17.3
GHSA-67jc-hmvg-q4c7Gogithub.com/NVIDIA/gpu-operator<25.3.225.3.2
GHSA-67jc-hmvg-q4c7Gogithub.com/NVIDIA/mig-parted<0.12.20.12.2
GO-2025-3998Gogithub.com/NVIDIA/gpu-operatorall versionsno fix published
GO-2025-3998Gogithub.com/NVIDIA/k8s-device-plugin<0.17.30.17.3
GO-2025-3998Gogithub.com/NVIDIA/mig-parted<0.12.20.12.2
GO-2025-3998Gogithub.com/NVIDIA/nvidia-container-toolkit<1.17.81.17.8

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 morenvidia-container-toolkit1.18.0-150200.5.17.1SUSE-SU-2025:4187-1
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20251023T162509-150000.1.110.1SUSE-SU-2025:3799-1
openSUSELeap 15.6govulncheck-vulndb0.0.20251023T162509-150000.1.110.1SUSE-SU-2025:3799-1
openSUSELeap 15.6nvidia-container-toolkit1.18.0-150200.5.17.1SUSE-SU-2025:4187-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgovulncheck-vulndb0.0.20251023T162509-1.1openSUSE-SU-2025:15666-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

RHEL AI is not affected because it uses CDI mode with NVIDIA Container Toolkit versions later than 1.17.5, which are not vulnerable, and does not rely on the enable-cuda-compat hook, thereby eliminating the attack vector entirely.

This vulnerability is rated as Important instead of Critical because, while it involves a symlink attack via the update-ldcache hook in the NVIDIA Container Toolkit, it has limited impact and specific requirements. The attacker needs low privileges inside a container and must use a specially crafted image to trigger the issue. It does not lead to code execution or privilege escalation, and it has no impact on confidentiality—only potential data tampering or denial of service. Additionally, the vulnerability affects only setups using this specific hook and can be easily mitigated by disabling it.

Red Hat's mitigation

This vulnerability can be mitigated by opting out using the enable-cuda-compat hook. When using the NVIDIA Container Runtime in legacy mode, you can opt out of using the enable-cuda-compat hook by editing the /etc/nvidia-container-toolkit/config.toml file to set the features.disable-cuda-compat-lib-hook feature flag to true:

[features]

disable-cuda-compat-lib-hook = true

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10toolboxNot affected
Red Hat Enterprise Linux 9toolboxNot affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-aws-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-azure-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-azure-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-gcp-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-intel-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/granite-3.1-8b-lab-v2.1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/granite-3.1-8b-starter-v2.1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/instructlab-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/instructlab-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/modelcar-granite-3-1-8b-lab-v2-1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/modelcar-granite-3-1-8b-starter-v2-1Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-23267.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON