The Yocto Project released version 6.0, codenamed “Wrynose”, and the series is already up to 6.0.1. It is an LTS (long-term support) release with four years of maintenance, guaranteed at least until April 2030. For anyone building embedded Linux, an LTS jump is not just another headline: it sets the base that products still on the market half a decade from now will be built on.
If you have never run into it, Yocto is not a distribution you install: it is a set of tools for building your own custom Linux distribution. Routers, cameras, cars, industrial machinery, consumer electronics — a huge amount of the Linux that never shows up on a desktop screen comes out of here.
Base and toolchain
Wrynose sits on the Linux 6.18 LTS kernel and refreshes the toolchain from top to bottom:
- GCC 15.2
- glibc 2.43
- LLVM 22.1
- Go 1.26
- Rust 1.94
The headline: compliance and traceability
What its developers emphasise most about this release is not the compiler version numbers, but three things: the four years of support, the improvements to SBOM and CVE tracking, and more secure defaults aimed squarely at easing compliance with the European Cyber Resilience Act (CRA).
That detail matters more than it looks. The CRA requires manufacturers selling software-bearing products in the EU to know exactly what is inside them and to manage their vulnerabilities across the device’s whole life. A decent SBOM (the software bill of materials) and CVE tracking that actually works stop being an engineering luxury and become a legal requirement. Yocto shipping that out of the box saves a lot of people an enormous amount of work.
Alongside it, a new Yocto Project Security Reference document has been added to the documentation, explaining how to report vulnerabilities to the project’s security team.
Rust enters the kernel
Another significant addition: Wrynose adds support for enabling Rust in the kernel and for building out-of-tree Rust kernel modules. Rust’s arrival in the Linux kernel has been a years-long saga, and an embedded build tool like Yocto supporting it natively is a fairly clear signal of where things are heading.
A plumbing change
Finally, a heads-up for anyone maintaining recipes: the Wic tool is now maintained in a separate project and is no longer part of OpenEmbedded-Core (OE-Core). It is not a disaster, but if your build flow assumes it lives inside OE-Core, that needs reviewing before you migrate.
Who should look at it
Anyone starting a new embedded product in the coming months. Beginning on a freshly released LTS buys you four years of calm, and doing it on one that already has the CRA homework half done saves you an awkward conversation later. If you have a live product on an earlier LTS, migration is less urgent, but it is worth planning.
The full breakdown is in the 6.0 (wrynose) release notes, and support dates are on the Yocto page.