Resolving Availability and Run-time Integrity Conflicts in Real-Time Embedded Systems

arXiv:2511.14088 · cs.CR · Submitted 2025-11-18 · Read on arXiv

cs.CR

Submitted: 2025-11-18

Updated: 2026-08-30

Code: https://github.com/RIOT-OS/RIOT

Terminology

• Core — 8× in this paper · explained in 2 episodes
• Verification — 6× in this paper · explained in 2 episodes
• Adam — 5× in this paper · explained in 2 episodes
• Integrity Monitor — 5× in this paper
• Availability Region — 3× in this paper
• Linear Temporal Logic — 3× in this paper
• Pointer Authentication — 3× in this paper
• Benchmark — 2× in this paper · explained in 2 episodes
• Control Flow Integrity — 2× in this paper
• Real-Time and Embedded Technology and Applications Symposium — 2× in this paper
• Accuracy — 1× in this paper · explained in 1 episode
• Branch Target Identification — 1× in this paper
• Elias — 1× in this paper · explained in 2 episodes
• Formal Verification — 1× in this paper · explained in 2 episodes
• Linear Temporal Logic (LTL) — 1× in this paper · explained in 4 episodes
• Trace — 1× in this paper · explained in 2 episodes

Sources

• TRACES: TEE-based Runtime Auditing for Commodity Embedded Systems
• Boosting Device Utilization in Control Flow Auditing

Related papers

• SoK: AI-Augmented Binary Reversing
• Relaxed Sender Anonymity for CBDC Interbank Settlement: A Zero-Knowledge Approach on Permissioned EVM
• Calibration-Family Overfit: Why Trusted Sabotage Monitors Don't Transfer Across Lineages
• Efficient Fuzzy PSI under One-Sided Assumptions
• Sealing the Audit-Runtime Gap for LLM Skills
• Token Composition: A Graph Based on EVM Logs