Broadwell MCE Bug
ConceptThe Broadwell MCE Bug is referenced in CPU-verification research as an example of a reported CPU hardware bug, alongside issues such as the Pentium FDIV bug and Ryzen segfault bug. In the provided evidence, it is used to motivate pre-deployment CPU bug detection and RTL verification, rather than described in implementation-level detail.
First seen 5/27/2026
Last seen 6/3/2026
Evidence 1 chunks
Wiki v1
WIKI
Overview
The Broadwell MCE Bug is cited in CPU-verification literature as one of several reported CPU hardware bugs. The cited work lists it alongside the Pentium FDIV bug and the Ryzen segfault bug as examples of notorious CPU bugs that can impose major mitigation and repair costs on manufacturers.[1]
Verification significance
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
3 connectionsCPU bug detection research mentions the Broadwell MCE bug as a notable hardware bug.
The Broadwell MCE bug is mentioned as one of numerous CPU bugs costing manufacturers billions.
The Broadwell MCE bug is mentioned as a real-world CPU bug motivating detection work.
LINKED ENTITIES
1 linksCITATIONS
3 sources3 citations — click to collapse
[1] The Broadwell MCE Bug is cited as one of several reported CPU bugs, alongside the Pentium FDIV bug and Ryzen segfault bug, and such bugs can impose major mitigation and repair costs. [2401.15967] Instiller: Towards Efficient and Realistic RTL Fuzzing
[2] The evidence argues that CPU circuits and RTL designs should be thoroughly verified before deployment because deployed hardware vulnerabilities are difficult to remove compared with software bugs. [2401.15967] Instiller: Towards Efficient and Realistic RTL Fuzzing
[3] The evidence describes CPU bug detection work using static and dynamic techniques and identifies fuzz testing as a promising CPU verification approach. [2401.15967] Instiller: Towards Efficient and Realistic RTL Fuzzing