Papers for

hardware quality assurance teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Power side channel guides fuzzer to find embedded system bugs

POZZER: A Power Side Channel-guided Fuzzer for Black-Box Embedded Systems

Abstract: Firmware fuzzing is an effective technique for discovering vulnerabilities in embedded systems. However, existing coverage-guided firmware fuzzers typically obtain feedback through firmware instrumentation, hardware debug interfaces, or firmware rehosting, which requires access to the firmware source code or binary image. Such requirements are often infeasible for off-the-shelf embedded devices, where firmware binaries are inaccessible, unrehostable, immodifiable, or undebuggable, necessitating fuzzing under black-box conditions. In this paper, we present POZZER, a power side-channel-guided fuzzer for black-box embedded systems. POZZER uses power traces as feedback to identify previously unseen behavior via an incrementally constructed graph-based representation of observed executions, guiding the fuzzer toward unexplored execution paths. Its non-profiling design requires neither prior firmware knowledge nor a clone device, extracting meaningful feedback from a single power trace per execution while remaining robust to measurement noise. We evaluate POZZER on 15 firmware targets across two platforms and two real-world commercial embedded devices. Across the resulting target-platform combinations, POZZER outperforms a blind fuzzer under the same time budget in 26 out of 30 target-platform combinations. Furthermore, POZZER discovers two previously unknown vulnerabilities in one of the commercial devices, both confirmed by the vendor, demonstrating its potential for identifying vulnerabilities in black-box embedded systems.

Sun 20 SeptCryptography and Security
The gist
Finding bugs in embedded device software is hard when the device’s internals are hidden. The authors created POZZER, a tool that listens to power usage patterns from the device to guess what it’s doing and find new software behaviors without needing to look inside. This helps POZZER test and find security problems even when the device firmware cannot be directly accessed or modified. The authors showed that POZZER worked better than a random tester on several devices and found real, previously unknown security flaws that were confirmed by the device maker.
Open → 2609.23583v1

Gpu memory safety evaluated with new standardized benchmark suite

Towards Standardized Evaluation of GPU Memory Safety with GMSBench

Abstract: As GPUs become increasingly integral to high-performance computing and machine learning, ensuring memory safety in GPU programs has become crucial for reliable and secure execution. However, evaluating GPU memory safety techniques remains challenging due to the lack of comprehensive and standardized benchmarks. In this paper, we present GMSBench, a GPU memory safety benchmark designed to evaluate a broad range of memory safety violations across different GPU memory spaces and execution scenarios. GMSBench comprises 149 self-contained CUDA tests spanning spatial, temporal, and concurrency errors. The suite provides a standardized foundation for the evaluation and comparative analysis of GPU memory safety mechanisms and helps expose gaps in their detection coverage. We demonstrate the utility of GMSBench by evaluating Compute Sanitizer, a widely used GPU memory error detection tool across multiple GPU architectures.

Tue 8 SeptCryptography and SecurityHardware Architecture
The gist
Memory bugs in programs that run on GPUs can cause crashes or security risks, but testing tools that find these bugs is hard without a common set of tests. The authors created GMSBench, a collection of 149 small CUDA tests that cover many types of memory errors in GPU programs. This benchmark helps see how well different tools catch these errors and reveals where they may miss problems. The authors used GMSBench to check one popular GPU debugging tool across several GPU types, showing how it can improve evaluation.
Open → 2609.08871v1