Linus Torvalds has officially announced the first Release Candidate (RC1) for Linux kernel 7.0, marking the start of public testing for the next major kernel series.
The release comes two weeks after Linux kernel 6.19 and the opening of the merge window for 7.0. Developers and testers can now begin evaluating the RC builds over the coming weeks.
Major Version Bump, Not Major Feature Shift
Despite the jump to version 7.0, Torvalds clarified that the new major version number does not signal a dramatic change in features.
According to Torvalds, the version bump follows the traditional numbering pattern rather than reflecting a single groundbreaking addition. The Linux project has not based major version changes on feature sets for many years.
Rust Support Now Stable
One of the most notable updates in Linux 7.0 is that Rust support is now officially stable, no longer labeled as experimental.
Rust has gradually been integrated into the Linux kernel to improve memory safety and reduce common programming errors. The 7.0 cycle also includes additional Rust-related improvements and updates.
Key Features in Linux 7.0
Beyond Rust stabilization, Linux kernel 7.0 introduces several technical enhancements:
- Support for atomic 64-byte loads on ARM processors
- Non-circular SQ entries to keep submission queue entries hot in cache
- Direct I/O support for the Btrfs file system when block size exceeds page size
- Initial support for the Btrfs remap-tree feature (experimental)
- Autonomous self-healing support for the XFS file system
- Support for SPI controllers with multiple data lanes
- BPF token access control integration with SELinux
- Support for ML-DSA post-quantum signatures
- LZMA compression enabled by default for the EROFS file system
These updates focus on performance improvements, security enhancements, and expanded hardware compatibility.
Expected Release Timeline
The final release of Linux kernel 7.0 is expected in mid-March 2026. If seven Release Candidates are issued, the stable version could arrive around March 12. If an eighth RC is required, release may shift to March 19.
Until then, developers and testers are encouraged to evaluate RC1 and provide feedback to ensure a stable final release.
