Linux 6.19 is here: HDR progresses and paves the way for Linux 7.0
The Linux kernel is preparing for a decade of change… at least in how it is named. After the release of Linux 6.19, Linus Torvalds confirmed that the next version will be called Linux 7.0 — not to celebrate a spectacular overhaul, but because the version numbers are becoming “too large” in his view.
This decision aligns with his pragmatic versioning philosophy, and it comes at a particularly symbolic time: when Rust transitions from curiosity to a permanent component of the kernel ecosystem.
A Linux 7.0 ‘Out of Mathematical Laziness’… Embraced
Torvalds has long considered major version jumps more about readability than disruption. In 2026, he echoes the same sentiment: after Linux 6.19, he prefers to start fresh with Linux 7.0 rather than piling up minor versions that eventually look like an inventory. In fact, the modern versioning has stabilized around a rhythm where a series often stretches to .19 before transitioning.
By the way, Linux 6.19 is not a ‘small’ kernel: it features improved support for older AMD GPUs via AMDGPU, advances in HDR (DRM Color Pipeline), and various hardware additions. But that is not the reason for the number change — just the context.
The Real Issue: Linux is Gradually Becoming Multilingual
Where the number is cosmetic, the internal evolution is much more substantial: the integration of Rust continues to expand. Rust was introduced to the kernel with Linux 6.1 (initial infrastructure), then gained traction release after release through abstractions and early practical uses.
The aim is simple yet brutal: to reduce the class of most costly bugs — use-after-free, buffer overflows, undefined behavior — by introducing memory safety options where relevant, especially for components such as drivers.
This is precisely the argument presented by the Rust-for-Linux project, and its progress is mature enough that the question is no longer “why,” but “how far.”
Rust, Yes… But Not Without Politics (or Friction)
The least ‘technical’ part may be the most delicate: governance. The kernel model relies on maintainers who are capable of reviewing and taking responsibility for code. Adding Rust compels either an upskilling process or structured trust in Rust contributors — and it has already generated debates on the LKML mailing list (integration cadence, scope, review responsibility).
LWN documented this tension point early on: how to coexist a “Rust tree” with maintainer lines by subsystems without breaking the review culture that underpins the strength of the project.
Why Linux 7.0 May “Sound” More Significant Than Its Predecessors
Technically, Linux will continue to evolve as it always has: incrementally. However, the kernel labeled 7.0 will arrive after several years of a rare transition: the official admission of a new language alongside C and assembly, with all that it implies in terms of tooling, processes, and mindsets.
Meanwhile, Linux is not stagnant on performance: CPU scheduling continues to modernize (EEVDF is now documented as the scheduling framework), and optimizing desktop/gaming responsiveness remains a focal point for the community.
In summary, Linux 7.0 is primarily a numbering choice. But, it might serve as a powerful symbol because it arrives at a time when Rust is moving from “experimental” to “structural” in the collective mindset of the kernel. And perhaps that is the real story: Linux is changing not through a “big bang,” but via gradual irreversibility.



