Cyber Resilience

CVE-2025-2953

Linuxfoundation Pytorch 2.6.0\+cu124

Public PoC
Published
30 March 2025
Modified
22 April 2025
CVSS Score v4 4.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0024 16th percentile
Risk Priority 25 floored blend · peak EPSS

Summary

CVE-2025-2953 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Linuxfoundation Pytorch. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as Deep Learning Frameworks; in the Data-Related Vulnerabilities risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability, which was classified as problematic, has been found in PyTorch 2.6.0+cu124. Affected by this issue is the function torch.mkldnn_max_pool2d. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed…

more

to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The security policy of the project warns to use unknown models which might establish malicious effects.

CWE(s)

AI Security AnalysisAI

AI Category
Deep Learning Frameworks
Risk Domain
Data-Related Vulnerabilities
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: pytorch

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-3730Same product: Linuxfoundation Pytorch
CVE-2025-55560Same product: Linuxfoundation Pytorch
CVE-2025-55558Same product: Linuxfoundation Pytorch
CVE-2025-55551Same product: Linuxfoundation Pytorch
CVE-2025-55554Same product: Linuxfoundation Pytorch
CVE-2025-63396Same product: Linuxfoundation Pytorch
CVE-2024-31583Same product: Linuxfoundation Pytorch
CVE-2025-55552Same product: Linuxfoundation Pytorch
CVE-2024-31580Same product: Linuxfoundation Pytorch
CVE-2025-2148Same product: Linuxfoundation Pytorch

Affected Assets

linuxfoundation
pytorch
2.6.0\+cu124

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include coding standards for correct resource allocation and release.

DE.CM-09 partial match
prevents

Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.

ID.AM-08 partial match
prevents

Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.

PR.IR-04 partial match
prevents

Capacity management helps surface leaks from unreleased resources but does not prevent the coding flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.

References