CVE-2025-63396
Summary
| CVE | CVE-2025-63396 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-11-12 21:15:52 UTC |
| Updated | 2026-06-17 09:53:04 UTC |
| Description | 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). |
Risk And Classification
Primary CVSS: v3.1 3.3 LOW from ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS: 0.001120000 probability, percentile 0.016240000 (date 2026-07-08)
Problem Types: CWE-667 | n/a | CWE-667 CWE-667 Improper Locking
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | ADP | DECLARED | 3.3 | LOW | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 3.3 | LOW | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Linuxfoundation | Pytorch | 2.5.0 | - | All | All |
| Application | Linuxfoundation | Pytorch | 2.7.1 | - | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/pytorch/pytorch/issues/156563 | [email protected] | github.com | Exploit, Issue Tracking |
| github.com/pytorch/pytorch | [email protected] | github.com | Product |
| github.com/Daisy2ang | [email protected] | github.com | Not Applicable |
| pytorch.com | [email protected] | pytorch.com | Product |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.