Process crash via out-of-bounds block argument read
Published May 5, 2023 · Updated Jan 29, 2025
Out-of-bounds read in LLVM MLIR One-Shot Bufferize allows local users to crash mlir-opt by processing crafted MLIR input. WhileOpInterface::verifyAnalysis requests a nonexistent block argument through Block::getArgument while analyzing an scf.while whose yielded values do not match its results. Exploitation requires a user to invoke mlir-opt with --one-shot-bufferize on attacker-controlled IR, and the demonstrated consequence is termination of that process.
Summary
What happened
Out-of-bounds read in LLVM MLIR One-Shot Bufferize allows local users to crash mlir-opt by processing crafted MLIR input. WhileOpInterface::verifyAnalysis requests a nonexistent block argument through Block::getArgument while analyzing an scf.while whose yielded values do not match its results. Exploitation requires a user to invoke mlir-opt with --one-shot-bufferize on attacker-controlled IR, and the demonstrated consequence is termination of that process.
The record
- CVE
- CVE-2023-29933
- Published
- May 5, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
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
- MLIR One-Shot Bufferize 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