Toolchain crash via malformed MLIR canonicalization
Published May 5, 2023 · Updated Jan 29, 2025
Memory-management flaw in LLVM MLIR allows context-dependent attackers to crash the toolchain via a crafted MLIR file. During canonicalization, DeduplicateAndRemoveDeadOperandsAndResults replaces operation uses, and IROperand::insertIntoCurrent faults while relinking the use-def chain. Exploitation requires a user to open the file with an affected MLIR tool, and the demonstrated consequence is a process crash without data disclosure or modification.
Summary
What happened
Memory-management flaw in LLVM MLIR allows context-dependent attackers to crash the toolchain via a crafted MLIR file. During canonicalization, DeduplicateAndRemoveDeadOperandsAndResults replaces operation uses, and IROperand::insertIntoCurrent faults while relinking the use-def chain. Exploitation requires a user to open the file with an affected MLIR tool, and the demonstrated consequence is a process crash without data disclosure or modification.
The record
- CVE
- CVE-2023-29932
- Published
- May 5, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- LLVM MLIR canonicalization crash reproducerproof 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