In a major stride toward the automotive industry’s digital transformation, Red Hat has achieved ISO 26262 ASIL-B functional safety certification for its In-Vehicle Operating System, officially validating it as a Safety Element out-of-Context (SEooC). This milestone signifies Red Hat’s position at the forefront of the software-defined vehicle (SDV) movement, offering automakers a secure, open-source platform tailored for safety-critical systems.
Further accelerating this shift, the company has launched a robust partner ecosystem—uniting silicon vendors, middleware providers, application developers, and systems integrators. Together, they aim to deliver pre-integrated, production-ready solutions that simplify development, reduce time to market, and unlock new possibilities for vehicle intelligence and performance.
The challenge, however, lies in navigating a fragmented hardware landscape. Each chip vendor brings unique architectures and optimisation demands. Red Hat’s response, said Francis Chow, VP and GM of In-Vehicle OS and Edge, is grounded in open standards and close collaboration. “The diversity of underlying silicon is a core challenge. We work closely with vendors to upstream hardware-specific software—especially drivers—into the mainline Linux kernel, cutting down fragmentation and easing integration,” he explained.
Linux’s proven portability and ubiquity across hardware platforms gives Red Hat a strong foundation. For out-of-tree components, the focus is on clean, maintainable integration without custom kernel patches. “Linux is not just powerful—it’s expected by many silicon partners,” Chow added, underscoring its role in simplifying long-term support and development.
Pre-integrating Middleware
The shift to software-defined vehicles brings with it the complex challenge of pre-integrating middleware—such as hypervisors and AUTOSAR stacks—with applications like ADAS, infotainment, and diagnostics, and services including OTA updates and cloud connectivity. Each layer, often developed by different vendors, must remain tightly synchronised across frequent updates.
According to Chow, maintaining this cohesion is one of the most pressing challenges in realising SDVs. “It’s a significant undertaking—but one that open source principles are uniquely positioned to solve.” He explained that transparency and collaboration, hallmarks of open source, help streamline integration throughout the development lifecycle, even as new updates are introduced.
Francis Chow
Crucially, the pervasiveness of Linux plays to Red Hat’s advantage. With a vast global developer base already building and testing on Linux, it has become the default environment for middleware and application development—often enabling early validation and reducing integration friction.
This cohesion is further strengthened by the industry's growing adoption of “cloud-first, shift-left development practices.” As more software components are built and tested in cloud environments, Linux serves as the common denominator—providing consistency from early design to in-vehicle deployment. For Red Hat, this shared foundation is key to ensuring that even the most layered and dynamic software stacks evolve in unison, he mentioned.
Real-Time Operating System
One of the defining complexities of software-defined vehicles is their need to simultaneously run time-sensitive, safety-critical functions—like braking or steering control—alongside less critical systems such as infotainment. Ensuring isolation, prioritisation, and deterministic performance is non-negotiable in this environment.
Red Hat In-Vehicle Operating System addresses this challenge with a layered approach. At its core, the OS is built on a PREEMPT_RT-enabled Linux scheduler, delivering soft real-time determinism for a broad range of automotive applications. For tasks demanding hard real-time, ultra-low latency performance, the company recognises the complementary role of both proprietary and open source RTOS platforms.
What sets it apart, however, is how it ensures robust isolation. Having achieved ISO 26262 ASIL-B functional safety certification, the OS is designed to guarantee 'freedom from interference' (FFI)—allowing QM and ASIL-B workloads to safely coexist within the same system image. This isolation is enforced through a combination of containerisation, memory protection, and fine-grained access control, ensuring that non-critical applications cannot compromise the integrity of safety-critical functions, he pointed out.
This approach not only ensures compliance and safety but also delivers greater resource efficiency and flexibility compared to traditional, hard-partitioning methods. It's a strategic differentiator that positions Red Hat’s platform as both future-ready and production-worthy for the software-defined automotive era.
Mitigating Security Threats
As vehicles become increasingly connected, the operating system must do more than manage performance—it must be secure by design. In the software-defined era, where cars interface with everything from firmware and bootloaders to cloud services, cybersecurity isn't an afterthought—it's foundational.
Chow underscores this imperative, stating that security is paramount in today’s connected vehicles. Red Hat embraces a holistic, layered security model, rooted in a secure development lifecycle and a strong focus on supply chain integrity. The company proactively identifies and patches vulnerabilities, prioritises rapid updates, and ensures all software is subjected to rigorous code reviews, comprehensive testing, and cryptographic signing—guaranteeing both authenticity and trust.
The company is also aligning its practices with the ISO/SAE 21434 standard, a key benchmark for automotive cybersecurity engineering. This commitment signals not only technical diligence but also a readiness to meet the industry’s most stringent security requirements, giving OEMs and Tier-1s confidence in a platform designed to protect, adapt, and evolve with the connected vehicle landscape, he mentioned.
Software Updates
Unlike legacy embedded systems, software-defined vehicles demand frequent and seamless software updates across their entire lifecycle. This constant evolution calls for a robust, agile operating system and integration framework—one capable of continuous deployment, validation, and rollback at a global scale.
Chow said Red Hat addresses this challenge by applying its enterprise-grade open source expertise to the automotive realm. The Red Hat In-Vehicle Operating System is backed by a structured update cadence—quarterly maintenance patches, annual minor releases, and major updates every three years—giving OEMs the flexibility to align updates with their development cycles and broader software stacks.
Crucially, its open-source foundation brings significant advantages. The very principles that underpin DevOps and continuous delivery—from rapid iteration to secure rollback—were refined in open-source ecosystems, with Linux at the core. Red Hat’s decades of leadership in this space translate into a proven model of consistent, reliable software delivery.
Equally vital is the company’s leadership in containerisation technologies, tailored specifically for automotive applications, he said. Containers allow modular updates, improved resource efficiency, and the isolation of dependencies—enabling safe, fine-grained updates across entire fleets. Combined with Red Hat’s continuous functional safety certification, this model gives automakers the confidence to update software as dynamically as any digital product—while ensuring safety, consistency, and control on the road.
Safe Deployment Across Diverse Vehicle Models & Applications
Ensuring a platform performs seamlessly across everything from entry-level city cars to premium flagship models is no small feat. According to Chow, the company meets this challenge through a foundation built on the time-tested stability of Red Hat Enterprise Linux (RHEL)—a platform trusted across industries from telecom and finance to industrial automation.
This stability gives its In-Vehicle Operating System the adaptability to serve a wide spectrum of automotive needs while maintaining modularity and reusability. Designed to scale with varying performance and safety requirements, the OS supports a broad range of underlying silicon, making it suitable for diverse vehicle classes.
Crucially, its ASIL-B functional safety certification as a Safety Element out-of-Context (SEooC) ensures it can be deployed across different vehicle models and applications without compromising safety. This modular, hardware-agnostic architecture allows OEMs to streamline development, reduce integration effort, and reuse software across platforms—bringing both flexibility and efficiency to the automotive value chain, he concluded.
Also Read:
Red Hat Achieves Milestone With ASIL-B Certified In-Vehicle Operating System