Process crash via empty argmin or argmax input
Published Jan 3, 2024 · Updated Jun 17, 2025
Divide-by-zero in PaddlePaddle before 2.6.0 allows attackers to crash a consuming process by passing an empty tensor to argmin or argmax. The CPU, GPU, and XPU ArgMinMax kernels accept an input whose numel() is zero and proceed without rejecting the empty reduction, triggering a floating-point exception. Reachability depends on a consuming application accepting attacker-influenced tensor data; exploitation interrupts that process without reported data disclosure or modification.
Summary
What happened
Divide-by-zero in PaddlePaddle before 2.6.0 allows attackers to crash a consuming process by passing an empty tensor to argmin or argmax. The CPU, GPU, and XPU ArgMinMax kernels accept an input whose numel() is zero and proceed without rejecting the empty reduction, triggering a floating-point exception. Reachability depends on a consuming application accepting attacker-influenced tensor data; exploitation interrupts that process without reported data disclosure or modification.
The record
- CVE
- CVE-2023-52313
- Published
- Jan 3, 2024
- Updated
- Jun 17, 2025
- Vendor
- PaddlePaddle
- Product
- PaddlePaddle
- Classifications
- CWE-369, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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.6.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.
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