Service interruption via incorrect trap-value reporting
Published Jul 18, 2022 · Updated Aug 3, 2024
Incorrect trap reporting in OpenHW Group CVA6 allows local users to interrupt service through ecall or ebreak instructions. The RTL writes the instruction encoding into the trap-value register instead of the faulting address or zero, so exception handlers receive incorrect trap metadata. Execution access in any processor privilege mode is sufficient; published evidence reports availability loss but does not identify whether the interruption is a hang, crash, or other failure.
Summary
What happened
Incorrect trap reporting in OpenHW Group CVA6 allows local users to interrupt service through ecall or ebreak instructions. The RTL writes the instruction encoding into the trap-value register instead of the faulting address or zero, so exception handlers receive incorrect trap metadata. Execution access in any processor privilege mode is sufficient; published evidence reports availability loss but does not identify whether the interruption is a hang, crash, or other failure.
The record
- CVE
- CVE-2022-34640
- Published
- Jul 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 18, 2022CVE 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.
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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- CVA6 ecall and ebreak reproducer test casesproof 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