Process crash or hang via unstopped profiler
Published Nov 12, 2025 · Updated Jul 5, 2026
Denial of service in PyTorch 2.5 and 2.7.1 allows local users to crash or hang a profiling process during result finalization. Accessing profiler.key_averages().table() before profiler.stop() leaves PythonTracer finalization without an orderly stop, causing a crash in 2.5 or a hang in 2.7.1. Local users must be able to run or influence profiling code, and the demonstrated consequence is limited to interruption of the affected process.
Summary
What happened
Denial of service in PyTorch 2.5 and 2.7.1 allows local users to crash or hang a profiling process during result finalization. Accessing profiler.key_averages().table() before profiler.stop() leaves PythonTracer finalization without an orderly stop, causing a crash in 2.5 or a hang in 2.7.1. Local users must be able to run or influence profiling code, and the demonstrated consequence is limited to interruption of the affected process.
The record
- CVE
- CVE-2025-63396
- Published
- Nov 12, 2025
- Updated
- Jul 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
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.
Public exploit references
- PyTorch profiler crash reproductionproof of concept · demonstrated
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