CVE-2025-3136Public exploit

Local process abort via live allocation deletion

Published Apr 3, 2025 · Updated Apr 3, 2025

Memory corruption in PyTorch 2.6.0 allows local users to interrupt a process by deleting a CUDA allocation that remains in use. torch.cuda.memory.caching_allocator_delete passes a live tensor pointer to the CUDA caching allocator's deletion path while the tensor still owns that allocation, causing an abort. Reachability requires local Python execution and an NVIDIA CUDA device; the published demonstration terminates only the invoking process, and PyTorch classifies invalid-argument crashes as ordinary bugs rather than security vulnerabilities.

CVSS severity4.8
Medium
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in PyTorch 2.6.0 allows local users to interrupt a process by deleting a CUDA allocation that remains in use. torch.cuda.memory.caching_allocator_delete passes a live tensor pointer to the CUDA caching allocator's deletion path while the tensor still owns that allocation, causing an abort. Reachability requires local Python execution and an NVIDIA CUDA device; the published demonstration terminates only the invoking process, and PyTorch classifies invalid-argument crashes as ordinary bugs rather than security vulnerabilities.

The record

CVE
CVE-2025-3136
Published
Apr 3, 2025
Updated
Apr 3, 2025
Vendor
PyTorch
Product
PyTorch
Classifications
CWE-119
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 3, 2025CVE publishedPublication date reported by the CVE source.
  2. Apr 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

PyTorch · PyTorchversion=2.6.0

Published CVSS scores

4.8VulDB CNACVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
1.7VulDB CNAAV:L/AC:L/Au:S/C:N/I:N/A:P
3.3VulDB CNACVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
3.3VulDB CNACVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo