Deterministic crash via unchecked CPUID call
Published Jan 29, 2021 · Updated Aug 3, 2024
Denial-of-service in Rust raw-cpuid before 9.0.0 allows local users to trigger deterministic crashes via unsupported CPUID calls. The native_cpuid::cpuid_count() function exposes the unsafe __cpuid_count() intrinsic as a safe function without checking whether the processor supports the requested instruction. The affected program must run on an x86 or x86_64 CPU lacking that CPUID support, and the consequence is a repeatable service crash without confidentiality or integrity impact.
Summary
What happened
Denial-of-service in Rust raw-cpuid before 9.0.0 allows local users to trigger deterministic crashes via unsupported CPUID calls. The native_cpuid::cpuid_count() function exposes the unsafe __cpuid_count() intrinsic as a safe function without checking whether the processor supports the requested instruction. The affected program must run on an x86 or x86_64 CPU lacking that CPUID support, and the consequence is a repeatable service crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2021-26307
- Published
- Jan 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-657, CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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
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