RISC-V is a free and open instruction set architecture (ISA) based on RISC design principles that has become a mainstream choice for embedded processors (including IoT devices) and high-performance research cores. The provided evidence portrays RISC-V as both an industry- and academia-relevant open ISA, and as a concrete target for hardware verification (formal, lockstep, constrained-random, symbolic execution, hardware fuzzing), security analysis (ROP, microarchitectural side channels, fault injection), benchmark generation, instruction-set simulation, and CPU fuzzing across many RISC-V processor implementations.
First seen5/25/2026
Last seen7/19/2026
Evidence450 chunks
Wikiv32
01
WIKI
Overview
RISC-V is a free and open instruction set architecture (ISA) based on RISC design principles. The provided evidence portrays RISC-V as both an industry- and academia-relevant open ISA that increasingly powers embedded processors (including IoT devices) and high-performance research cores, and as a concrete target for verification, security analysis, fault-injection modeling, benchmark generation, instruction-set simulation, and CPU fuzzing across multiple RISC-V processor implementations.
[1]RISC-V is a free and open instruction set architecture (ISA) based on RISC design principles, becoming a mainstream choice for embedded processors (including IoT devices), and the RISC-V community is studying security solutions aimed at achieving a root of trust (RoT) and preventing tampering or leakage of sensitive information on RISC-V devices.A Survey on RISC-V Security: Hardware and Architecture
[2]RISC-V is an open-source hardware ISA based on RISC design principles; RISC-V ROP has been demonstrated to be Turing complete and capable of arbitrary function calls using GNU libc gadgets, with algorithmic ROP-chain generation compiling arbitrary code into RISC-V ROP chains.Return-Oriented Programming in RISC-V
[3]Google RISCV-DV is a SV/UVM-based open-source instruction generator for RISC-V processor verification supporting RV32IMAFDC and RV64IMAFDC, machine/supervisor/user privilege modes, page-table randomization, privileged-CSR tests, trap/interrupt handling, MMU stress tests, sub-program generation, illegal/HINT instructions, random branches, directed/random mixing, debug mode with randomized debug ROM, an instruction-generation coverage model, SV testbench handshaking, and co-simulation with spike, riscv-ovpsim, and sail-riscv; it has been verified with Synopsys VCS, Cadence Incisive/Xcelium, and Mentor Questa, and is also reported to work with dsim.third_party/tests/IbexGoogle - third_party/Surelog - Git at Google
[4]The RISCV-DV IbexGoogle flow is applied to LowRISC Ibex, extends RISCV-DV via the user_extension directory and --custom_target/--isa/--mabi/--sim_opts=+uvm_set_type_override invocation, and exposes a handshaking mechanism (HANDSHAKE.md), a Spike-based functional coverage flow via cov.py and riscv_instr_cover_group.sv, runtime options such as instr_cnt, num_of_sub_program, illegal_instr_ratio, hint_instr_ratio, boot_mode, no_wfi, no_dret, gen_debug_section, set_dcsr_ebreak, and a YAML testlist.yaml driving run.py with --test, --iterations, --iss spike|ovpsim|sail[,...], --isa, --mabi, --steps, --co, --seed, --verbose, --target, --custom_target, and --simulator options.third_party/tests/IbexGoogle - third_party/Surelog - Git at Google
[5]PORTRUSH is a hardware-fuzzing framework that constructs a Write Request Graph (WRG) to model arbitration/priority among RISC-V CPU write entities, uses Hierarchical Aggregation and Decoding of selection-element signals to detect write-port contention, and drives a Contention-guided Hardware Fuzzing loop that combines contention-triggering instruction sequences with transient/speculative execution attack patterns; it was evaluated on BOOM, NutShell, and Rocket Core RISC-V CPUs.PORTRUSH: Detect Write Port Contention Side-Channel Vulnerabilities via Hardware Fuzzing
[6]PORTRUSH reports two novel write-port contention side-channel attacks on RISC-V CPUs: MSHRush (LSU vs. Miss Status Handling Register contention at the L1 data cache, demonstrated on BOOM) and Birgus-variant (physical register file contention in the Reorder Buffer, demonstrated on NutShell), as well as the known Spectre-STC attack on BOOM, and notes that write-port contention side channels can leak information even in processors with secure or partitioned caches.PORTRUSH: Detect Write Port Contention Side-Channel Vulnerabilities via Hardware Fuzzing
[7]Alpinum's RISC-V verification blog describes a coverage-driven RISC-V verification loop combining architectural tests, constrained-random generation, formal checks, lockstep comparison, and software-driven scenarios, and lists riscv-arch-test, Google riscv-dv, RISCOF, YosysHQ riscv-formal, the RISC-V Instruction Set Manual Volume I, the RISC-V Debug Specification, and the OpenHW Group CORE-V Verification Strategy as supporting infrastructure.RISC-V Verification: Five Places Projects Lose Weeks