Process crash via unchecked JIT tuple inputs
Published Apr 17, 2024 · Updated Mar 28, 2025
Heap buffer overflow in PyTorch before 2.2.0 allows attackers to crash a process through malformed JIT tuple bytecode. The tupleConstruct function fails to verify that num_inputs does not exceed the interpreter stack size before accessing tuple inputs. Triggering the flaw requires a target process to execute the crafted JIT input; the reported consequence is a process crash.
Summary
What happened
Heap buffer overflow in PyTorch before 2.2.0 allows attackers to crash a process through malformed JIT tuple bytecode. The tupleConstruct function fails to verify that num_inputs does not exceed the interpreter stack size before accessing tuple inputs. Triggering the flaw requires a target process to execute the crafted JIT input; the reported consequence is a process crash.
The record
- CVE
- CVE-2024-31580
- Published
- Apr 17, 2024
- Updated
- Mar 28, 2025
- Vendor
- PyTorch
- Product
- PyTorch
- Classifications
- CWE-122, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Mar 28, 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.
- Affected versionversion=0 <2.2.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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