Red Hat gives automotive Rust a qualified path onto In-Vehicle OS

Red Hat and Ferrous Systems have set out a qualified route for using Rust on Red Hat In-Vehicle Operating System, pairing Ferrous Systems' Ferrocene toolchain with the automotive platform. The immediate deliverable is a supported compilation target in Ferrocene 26.05; the companies say full general availability of the joint solution is planned for the second half of 2027.

What changed

Ferrocene 26.05 now supports the aarch64-rhivos2-linux-gnu target for Red Hat In-Vehicle Operating System 2 on Armv8-A. That gives automotive teams a defined toolchain and target for developing and testing Rust applications now, rather than waiting for the complete joint offering.

The safety claim has important boundaries. Red Hat says the Ferrocene toolchain is qualified under ISO 26262 up to ASIL D, while a certified subset of Rust's core library is available for ISO 26262 ASIL B workloads. The target manual further specifies that qualified use requires cross-compilation from the matching Red Hat Enterprise Linux 10 host on aarch64, using the version named by the RHIVOS 2 documentation. The target supports RHIVOS 2 on aarch64 with glibc 2.31 or later.

This is therefore a usable development path today, but not yet the generally available combined solution. Red Hat says developers can write, test and validate Rust workloads on In-Vehicle OS while platform certification is completed. The planned H2 2027 general availability is aligned with safety-certified Red Hat In-Vehicle OS releases.

Who it affects

The announcement is aimed at automakers, Tier 1 suppliers and automotive software teams building safety-related applications. It is particularly relevant to teams that want Rust's memory-safety properties without replacing an existing codebase in one move.

Red Hat and Ferrous Systems say the integration supports mixed Rust and C/C++ environments. Safety-critical Rust components can interoperate with existing C and C++ automotive stacks, providing a gradual migration path rather than requiring a wholesale rewrite.

What teams should do

Teams evaluating the path can begin development and testing with Ferrocene 26.05 and the aarch64-rhivos2-linux-gnu target. They should treat the host environment as part of the qualification boundary: build from the matching RHEL 10 aarch64 host described by the RHIVOS 2 assumptions of use, and verify the required compiler and linker setup in the target manual.

Qualification materials are available from Ferrous Systems as teams move toward functional-safety certification. The public target manual is marked as a development-branch preview that may be incomplete or inaccurate, so production programs should confirm requirements against the applicable customer documentation and the exact RHIVOS 2 release they intend to certify.