Process crash via empty FFT axes
Published Apr 3, 2025 · Updated Apr 3, 2025
Memory corruption in MindSpore 2.5.0 allows local users to crash a process by calling mindspore.numpy.fft.rfft2 with empty axes. The rfft2 path processes an empty axes tuple and terminates with a segmentation fault instead of returning a result or rejecting the input. The published reproduction requires local Python execution and affects the invoking process, with no reported confidentiality or integrity impact.
Summary
What happened
Memory corruption in MindSpore 2.5.0 allows local users to crash a process by calling mindspore.numpy.fft.rfft2 with empty axes. The rfft2 path processes an empty axes tuple and terminates with a segmentation fault instead of returning a result or rejecting the input. The published reproduction requires local Python execution and affects the invoking process, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2025-3145
- Published
- Apr 3, 2025
- Updated
- Apr 3, 2025
- Vendor
- MindSpore
- Product
- MindSpore
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=2.5.0
What conditions does exploitation require?
What is affected?
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
- Empty-axes rfft2 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