The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

DifuzzRTL: Differential Fuzz Testing to Find CPU Bugs

The work

AuthorsJaewon Hur; Suhwan Song; Dongup Kwon; Eunjin Baek; Jangwoo Kim; Byoungyoung Lee
Editors
Typemisc
Year2021
Citekeyhur2021difuzzrtl

Where it appeared

Published inProceedings - IEEE Symposium on Security and Privacy/Proceedings of the ... IEEE Symposium on Security and Privacy
PublisherIEEE Computer Society
Pages1286--1303

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

Security bugs in CPUs have critical security impacts to all the computation related hardware and software components as it is the core of the computation. In spite of the fact that architecture and security communities have explored a vast number of static or dynamic analysis techniques to automatically identify such bugs, the problem remains unsolved and challenging largely due to the complex nature of CPU RTL designs.This paper proposes DIFUZZRTL, an RTL fuzzer to automatically discover unknown bugs in CPU RTLs. DIFUZZRTL develops a register-coverage guided fuzzing technique, which efficiently yet correctly identifies a state transition in the finite state machine of RTL designs. DIFUZZRTL also develops several new techniques in consideration of unique RTL design characteristics, including cycle-sensitive register coverage guiding, asynchronous interrupt events handling, a unified CPU input format with Tilelink protocols, and drop-in-replacement designs to support various CPU RTLs. We implemented DIFUZZRTL, and performed the evaluation with three real-world open source CPU RTLs: OpenRISC Mor1kx Cappuccino, RISC-V Rocket Core, and RISC-V Boom Core. During the evaluation, DIFUZZRTL identified 16 new bugs from these CPU RTLs, all of which were confirmed by the respective development communities and vendors. Six of those are assigned with CVE numbers, and to the best of our knowledge, we reported the first and the only CVE of RISC-V cores, demonstrating its strong practical impacts to the security community.

How it got here

How it got hereagent via openalex
Added2026-10-24 21:58 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@misc{hur2021difuzzrtl,
  title        = {DifuzzRTL: Differential Fuzz Testing to Find CPU Bugs},
  author       = {Jaewon Hur and Suhwan Song and Dongup Kwon and Eunjin Baek and Jangwoo Kim and Byoungyoung Lee},
  year         = {2021},
  journal      = {Proceedings - IEEE Symposium on Security and Privacy/Proceedings of the ... IEEE Symposium on Security and Privacy},
  publisher    = {IEEE Computer Society},
  pages        = {1286--1303},
  doi          = {10.1109/sp40001.2021.00103},
}

This record lives at https://refs.drheap.org/hur2021difuzzrtl/ and will keep doing so.