VehicleSec 26 - RVDebloater: Mode-based Adaptive Firmware Debloating for Robotic Vehicles @UsenixOrg
VehicleSec 26 - RVDebloater: Mode-based Adaptive Firmware Debloating for Robotic Vehicles  @UsenixOrg
Uploaded September 2026 | Updated November 2026, 3 days ago
RVDebloater: Mode-based Adaptive Firmware Debloating for Robotic Vehicles

Mohsen Salehi and Karthik Pattabiraman, The University of British Columbia

Embedded firmware is becoming increasingly larger, thereby expanding its attack surface. Despite the increase in firmware size, many embedded devices, such as robotic vehicles (RVs), operate in distinct modes, each requiring only a small subset of the firmware code at runtime. Debloating is an approach to reduce attack surfaces by removing or restricting unneeded code. Unfortunately, existing techniques suffer from significant limitations, such as coarse granularity and irreversible code removal, limiting their applicability. We propose RVDebloater, a novel adaptive debloating technique for \textit{mode-based embedded devices} such as RVs that automatically identifies unneeded firmware code for each mode using either static or dynamic analysis, and dynamically debloats the firmware for each mode at the function level at runtime. RVDebloater uses a software-based enforcement approach to ensure that only the required functionalities are accessible from each mode and supports diverse \textit{mode-based embedded devices}.
We implemented RVDebloater using the LLVM compiler and evaluated its efficiency and effectiveness on six different RVs, including both simulated and real ones, with different real-world missions. We find that device requirements change throughout its lifetime for each mode, and that many critical firmware functions can be restricted in other modes, with an average of 85% of functions not being required. The results showed that none of the missions failed after debloating with RVDebloater, indicating that it neither incurred false positives nor false negatives. Further, RVDebloater prunes the firmware call graph by an average of 45% across different firmware. Finally, RVDebloater incurred an average performance overhead of 3.9% and memory overhead of 4% (approximately 0.25 MB) on real RVs, and also prevented three real attacks.

View the full VehicleSec '26 program at usenix.org/conference/vehiclesec26/program
VehicleSec 26 - RVDebloater: Mode-based Adaptive Firmware Debloating for Robotic VehiclesSREcon26 Europe/Middle East/Africa - How We Troubleshoot Difficult Problems: Cognition and...USENIX Security 26 - Transparent Dictionaries from Polynomial CommitmentsSREcon26 Europe/Middle East/Africa - The Optimization We Didnt BuildSREcon26 Europe/Middle East/Africa - Pull Requests Are Dead, Long Live Peer ReviewNSDI 25 - Enabling Portable and High-Performance SmartNIC Programs with AlkaliUSENIX Security 26 (Enigma Track) - Youth Digital Immersion: Cyber Readiness Builds Mental...USENIX Security 26 - Five Queries Are Enough: Query-Efficient and Surrogate-Free Membership Infere…USENIX Security 26 - MATE: Policy-Aware Security Auditing for Mobile Agents via Synthesis-Driven T…USENIX Security 25 - Secure Caches for Compartmentalized SoftwareWOOT 26 - Are Neuro-Inspired Multi-Modal Vision-Language Models Resilient to Membership...WOOT 26 - Onelogon: Taking over Active Directory Accounts via Netlogon
USENIX |

VehicleSec '26 - RVDebloater: Mode-based Adaptive Firmware Debloating for Robotic Vehicles

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER