Safety-critical Linux means running Linux where a failure can injure someone: in cars, industrial robots, and medical devices. You cannot certify the whole kernel the way a small safety controller is certified, so the industry does something different. It certifies a defined Linux configuration as a Safety Element out of Context, with documented assumptions about how it is used, wraps it in a small high-integrity monitor and hardware partitioning so a fault cannot spread, and keeps that certification current as the code changes. For embedded engineers this creates a durable new skill set built around safety architecture, not just kernel code.
For most of its history, Linux was kept out of the part of a product that can hurt people. It ran the dashboard, not the brakes; the hospital display, not the infusion pump's dosing loop. That line is now moving. Software-defined vehicles, surgical robots, and industrial automation want one capable operating system across the whole device, and increasingly that operating system is Linux. Safety-critical Linux is the effort to let Linux take those roles without lowering the safety bar. This article explains why it is hard, how it is actually being done, and what the shift means for embedded and kernel engineers.
