Exception-handling corruption via blocked EEAR writes
Published Apr 18, 2023 · Updated Mar 5, 2025
Register-write failure in the mor1kx processor allows context-dependent attackers to corrupt exception-handling control flow. The controller logic in mor1kx_ctrl_cappuccino.v omits an mtspr write path for EEAR, so even supervisor-mode writes leave the register unchanged. Code must execute at an authorized privilege level and invoke an exception path that rewrites EEAR; affected handlers then use stale effective-address state.
Summary
What happened
Register-write failure in the mor1kx processor allows context-dependent attackers to corrupt exception-handling control flow. The controller logic in mor1kx_ctrl_cappuccino.v omits an mtspr write path for EEAR, so even supervisor-mode writes leave the register unchanged. Code must execute at an authorized privilege level and invoke an exception path that rewrites EEAR; affected handlers then use stale effective-address state.
The record
- CVE
- CVE-2021-41613
- Published
- Apr 18, 2023
- Updated
- Mar 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1201
- Attack vector
- Unavailable
- Privileges
- admin
Timeline
How it unfolded
- Apr 18, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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
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