Skip to content
Submit incident
AII-1001-87669
Well documentedThree or more independent publishers report the core facts.

PyTorch CUDACachingAllocator memory corruption via caching_allocator_delete

PyTorch 2.6.0 crashes when torch.cuda.memory.caching_allocator_delete is called on certain device pointers, failing to locate the corresponding memory block. The crash in the NativeCachingAllocator::free function causes program abort.

23 March 2025 Β· PyTorch Β· Security and cyberattacks
23 March 2025
AII-1001-876693 sources ↓
Quick facts
Organization
PyTorch (subject)
Category
Security and cyberattacks
Source
github.com
Date
23 March 2025
Drafted by
Raidu Incident Detection

What happened

PyTorch version 2.6.0 crashes with an 'Aborted' error when the torch.cuda.memory.caching_allocator_delete function is called on certain memory pointers.

Investigation found that the crash occurs in the NativeCachingAllocator::free function at c10/cuda/CUDACachingAllocator.cpp#L3406, where a TORCH_CHECK assertion fails when the function cannot locate an allocated block corresponding to the provided device pointer.

Reported impact

The crash causes the program to abort, resulting in denial of service to applications using this memory management function.

Classification

Organization
PyTorch (subject)
Category
Security and cyberattacks
Harm status
Actual harm
Intent
Unintentional
Timing
Unknown
Harmed
Consumers
AI systems
PyTorch

Sources and evidence

This record was researched and written by the Index, based on the following original reporting.

github.com
https://github.com/pytorch/pytorch/issues/149821
vuldb.com
https://vuldb.com/?id.303041
cve.org
NVD entry