CVE-2025-63396: Low severity PyTorch PyTorch vulnerability
Published Nov 12, 2025
·Updated
An issue was discovered in PyTorch v2.5 and v2.7.1. Omission of profiler.stop() can cause torch.profiler.profile (PythonTracer) to crash or hang during finalization, leading to a Denial of Service (DoS).
Affected Software
4 affected components
PyTorch PyTorch>=2.5<=2.7.1
linuxfoundation Pytorch Python=2.5.0
linuxfoundation Pytorch Python=2.7.1
IBM watsonx.data intelligence<=5.2.0, 5.2.1, 5.3.0, 5.3.1
Event History
Nov 12, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 27, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-63396?
CVE-2025-63396 is classified as a Denial of Service (DoS) vulnerability.
2
How do I fix CVE-2025-63396?
To fix CVE-2025-63396, ensure that profiler.stop() is called to prevent crashes or hangs during finalization.
3
Which versions of PyTorch are affected by CVE-2025-63396?
CVE-2025-63396 affects PyTorch versions 2.5 and 2.7.1.
4
What symptoms indicate a problem related to CVE-2025-63396?
Symptoms of CVE-2025-63396 include the PyTorch profiler crashing or hanging during finalization.
5
Is there a workaround for CVE-2025-63396 if I cannot update PyTorch?
A potential workaround for CVE-2025-63396 is to manually ensure that profiler.stop() is invoked in your profiling code.