Processing errors via stale mstatus SD bit
Published Feb 6, 2025 · Updated Feb 11, 2025
Incorrect mstatus handling in RSD commit 3d13a allows attackers to trigger processing errors by setting the FS field to 11. An mstatus write of 0x00007800 leaves the register at that value rather than setting the SD bit and producing 0x80007800 as required. Public sources do not explain how attackers reach this processor state or what security boundary the stale SD bit crosses.
Summary
What happened
Incorrect mstatus handling in RSD commit 3d13a allows attackers to trigger processing errors by setting the FS field to 11. An mstatus write of 0x00007800 leaves the register at that value rather than setting the SD bit and producing 0x80007800 as required. Public sources do not explain how attackers reach this processor state or what security boundary the stale SD bit crosses.
The record
- CVE
- CVE-2024-25883
- Published
- Feb 6, 2025
- Updated
- Feb 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-682
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 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.
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
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