{"id":278,"date":"2026-04-30T06:47:20","date_gmt":"2026-04-30T06:47:20","guid":{"rendered":"https:\/\/marcoferrigno.net\/?p=278"},"modified":"2026-04-30T06:47:24","modified_gmt":"2026-04-30T06:47:24","slug":"linux-kernel-7-0-the-quiet-revolution-that-changes-everything","status":"publish","type":"post","link":"https:\/\/marcoferrigno.net\/it\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/","title":{"rendered":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">While the industry chases the next AI benchmark and the next model announcement, something genuinely important happened on <strong>April 12, 2026<\/strong>, and it arrived with almost no fanfare: Linus Torvalds released <strong>Linux kernel 7.0<\/strong>. The announcement was accompanied by a typically deadpan Torvalds joke \u2014 he bumped the major version, he said, because 6.19 was getting difficult to count on his fingers and toes. No architectural break. No marketing slide. A merge window, seven release candidates, a tarball on kernel.org, a signature to verify.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is what real infrastructure looks like when it works. It&#8217;s patient. It&#8217;s incremental. It doesn&#8217;t ask you to be excited. And if you&#8217;ve been paying attention to the right signals, Linux 7.0 is one of the most consequential kernel releases in years \u2014 not because any single feature is revolutionary, but because <strong>five long-running engineering efforts reach maturity in the same cycle<\/strong>. Rust graduates from experimental. XFS becomes self-healing. KVM virtualizes AMD&#8217;s ERAPS. Module signing gets post-quantum cryptography. And, as a quiet reminder of what &#8220;long-term support&#8221; really means, the kernel continues to ship patches for SPARC and DEC Alpha.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This post tells each of those stories. Not as a feature list, but as evidence of what it takes to build infrastructure you can actually trust over decades.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png\" alt=\"\" class=\"wp-image-293\" srcset=\"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png 1024w, https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-300x169.png 300w, https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-768x432.png 768w, https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1536x864.png 1536w, https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-18x10.png 18w, https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<!--more-->\n\n\n\n<h3 class=\"wp-block-heading\">Index<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"#rust\">The Memory Safety Story: Rust, No Longer Experimental<\/a><\/li>\n\n\n\n<li><a href=\"#xfs\">The Filesystem Story: XFS Learns to Heal Itself<\/a><\/li>\n\n\n\n<li><a href=\"#eraps\">The Virtualization Story: AMD ERAPS Meets KVM<\/a><\/li>\n\n\n\n<li><a href=\"#mldsa\">The Post-Quantum Story: ML-DSA Arrives in the Kernel<\/a><\/li>\n\n\n\n<li><a href=\"#heritage\">The Heritage Story: SPARC and Alpha Still Alive<\/a><\/li>\n\n\n\n<li><a href=\"#conclusion\">What This Release Actually Means<\/a><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"rust\">The Memory Safety Story: Rust, No Longer Experimental<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For four decades, the Linux kernel has been written in C. This is not a detail \u2014 it is the defining technical constraint of the project. C delivers extraordinary performance and complete control over the machine, and in return it demands that every developer be personally responsible for memory safety. <strong>Use-after-free, null pointer dereferences, buffer overflows, data races<\/strong>: entire categories of vulnerabilities exist because C cannot prevent them at compile time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The cost of this bargain is not theoretical. A substantial fraction of every kernel CVE in the past decade traces back to memory safety errors that the compiler, structurally, could not catch. Google&#8217;s Android security team has been publishing on this for years. Microsoft&#8217;s security response team has said the same thing about Windows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The Rust for Linux project<\/strong> has been arguing since 2020 that there is a way out: a language with C&#8217;s performance and control but with memory safety enforced by the compiler. The project moved cautiously \u2014 experimentally \u2014 through kernel cycles. Drivers were written. The Android Binder driver, rewritten in Rust, shipped on hundreds of millions of Android devices. The build infrastructure matured.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At the <strong>2025 Linux Maintainer Summit in Tokyo<\/strong>, the kernel maintainers made the decision formal. Linux 7.0 is the release where the <code>[EXPERIMENTAL]<\/code> warning comes off.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What this means practically:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Rust is now a <strong>first-class language<\/strong> in the kernel tree alongside C<\/li>\n\n\n\n<li>New driver submissions in Rust are reviewed to the same standard as C code<\/li>\n\n\n\n<li>Distribution toolchains (Fedora 44, Ubuntu 26.04 LTS) now ship Rust build support enabled by default<\/li>\n\n\n\n<li>The NVMe subsystem has active Rust rewrite proposals \u2014 watch this space in 7.1 and 7.2<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to build a 7.0 kernel with Rust support enabled, the toolchain check is your first stop:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd linux-7.0\nmake rustavailable\n# Expected output: Rust is available!\n\nscripts\/config --enable CONFIG_RUST\nmake olddefconfig\nmake -j$(nproc)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>make rustavailable<\/code> fails, the script at <code>scripts\/min-tool-version.sh<\/code> will tell you the minimum <code>rustc<\/code> version required. Most distributions now package a compatible toolchain, but if you&#8217;re building on an older LTS you may need <code>rustup<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The kernel will not be rewritten in Rust. C remains the lingua franca, and anyone predicting otherwise misunderstands the project. What Rust&#8217;s stabilization actually does is <strong>give maintainers a tool they didn&#8217;t have before<\/strong>: the option to write new, security-critical, memory-dangerous code in a language that eliminates an entire class of vulnerabilities at compile time. This is one of those slow, patient infrastructure changes that will shape the security properties of Linux systems for the next twenty years.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"xfs\">The Filesystem Story: XFS Learns to Heal Itself <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you operate Linux at any scale, you probably run XFS. It is the default filesystem on <strong>RHEL, Rocky Linux, AlmaLinux<\/strong>, and most server-oriented distributions. It was designed in 1994 at Silicon Graphics for workloads that punished lesser filesystems \u2014 scientific computing, video editing, high-throughput storage. It has been the dependable choice for enterprise Linux for a generation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And until Linux 7.0, it had a brittle failure mode. When XFS detected metadata corruption \u2014 typically caused by a power failure, a bad sector, or a controller fault \u2014 its response was deterministic and operationally painful:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91; 183.442610] XFS (sda1): Metadata corruption detected at xfs_inode_buf_ops\n&#91; 183.442618] XFS (sda1): Unmount and run xfs_repair<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Translate that message into operational reality: take the volume offline, boot from rescue media, run <code>xfs_repair<\/code>, pray that the damage is confined to metadata and not user data, and explain to stakeholders why the system was down. On a live root filesystem, the unmounting requirement is a nightmare. On a container host with dozens of running services, it&#8217;s a cascade failure waiting to propagate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Linux 7.0 introduces <strong>autonomous self-healing<\/strong>. The design principle is elegant: XFS already maintains redundant copies of critical metadata \u2014 inode btrees, allocation group headers, directory blocks. The new healing logic detects corruption at read time, cross-references the redundant copies, reconstructs the correct data in place, and continues operation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91; 183.442610] XFS (sda1): Repairing corrupt inode btree in AG 2.\n&#91; 183.442618] XFS (sda1): Self-healing complete. Filesystem operational.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is not a replacement for RAID. It is not a replacement for backups. It is not protection against physical data loss that exceeds what XFS internally duplicates. <strong>It is protection against the single most common class of real-world metadata corruption events<\/strong> \u2014 the ones that have historically required human intervention and caused production outages. On a 7.0 kernel with a standard XFS-formatted volume, this activates automatically. No configuration change. No opt-in. Mount the volume, use it, and when something goes wrong at the metadata layer the filesystem quietly fixes itself and logs what it did.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Operational monitoring is straightforward:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Watch self-healing events in real time\nwatch -n 2 'dmesg | grep -i \"xfs.*heal\\|xfs.*repair\"'\n\n# Full filesystem integrity check without unmounting\nxfs_info \/dev\/sda1\nxfs_db -r -c \"check\" \/dev\/sda1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you manage a fleet of XFS-backed servers, adding <code>xfs.*heal<\/code> patterns to your centralized log aggregation (Loki, Elastic, Splunk, whatever) is fifteen minutes of work and gives you visibility into a whole category of events you previously could only detect after they had caused an outage.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"eraps\">The Virtualization Story: AMD ERAPS Meets KVM <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the feature with the most nuance, and the one most frequently described imprecisely. It deserves careful explanation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>ERAPS<\/strong> stands for <em>Enhanced Return Address Predictor Security<\/em>. It is a feature introduced on <strong>AMD Zen 5 processors<\/strong> \u2014 the 5th generation EPYC, codename &#8220;Turin.&#8221; To understand why it matters, we need to briefly revisit the speculative execution attacks of the past eight years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In 2018, the <strong>SpectreRSB<\/strong> vulnerability demonstrated that the Return Stack Buffer (RSB) \u2014 the hardware structure that predicts the target of <code>RET<\/code> instructions during speculative execution \u2014 could be poisoned by an attacker to redirect speculation to attacker-controlled addresses. This could leak kernel memory to userspace, or host memory to guest VMs, through side-channel timing analysis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The software mitigation that followed was <strong>RSB stuffing<\/strong>: on every context switch and every VMEXIT, the kernel executes 32 <code>CALL<\/code> instructions to overwrite the RSB with safe targets. This works. It also has a real, measurable performance cost \u2014 particularly in virtualization-heavy workloads, where VMEXITs are frequent. Eight years later, every Linux system running on AMD or Intel silicon is still paying this performance tax.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ERAPS is the hardware answer. On Zen 5, two things change:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>TLB flushes automatically trigger RSB flushes<\/strong>, eliminating the need for explicit software-driven RSB stuffing at the most common stuffing-trigger points.<\/li>\n\n\n\n<li><strong>The RSB is expanded to 64 entries<\/strong> in VM contexts (previous AMD generations had 32).<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">What Linux 7.0 does, specifically, is add the initial support in KVM&#8217;s AMD SVM code to <strong>virtualize ERAPS for guest VMs<\/strong>. When ERAPS is exposed to the guest:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The guest can reduce or eliminate its own RSB stuffing on context switches<\/li>\n\n\n\n<li>The guest benefits from the hardware&#8217;s automatic RSB flush on CR3 writes<\/li>\n\n\n\n<li>The guest can safely raise its RSB stuffing loop count from the hardcoded 32 to match the actual 64-entry hardware RSB<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This is the important distinction that sometimes gets lost: <strong>ERAPS is not merely a security feature, it&#8217;s a performance recovery feature<\/strong>. It reduces the software mitigation tax that Spectre imposed. For EPYC Turin virtualization hosts running latency-sensitive guest workloads \u2014 databases, busy JVMs, microservices with high context-switch rates \u2014 this will be measurable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One important caveat: ERAPS virtualization in 7.0 requires NPT (Nested Page Tables) to be enabled in KVM. This is the standard configuration for any production KVM deployment, so in practice it&#8217;s a non-issue. Shadow paging configurations do not benefit from the automatic RSB flush on guest context switches and would require additional hypervisor-side mitigation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verifying ERAPS after booting 7.0 on Zen 5 hardware:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># On the host: confirm ERAPS is enumerated by the CPU\ngrep -m1 \"eraps\" \/proc\/cpuinfo\n\n# Check that KVM exposes ERAPS to guests\ncat \/sys\/module\/kvm_amd\/parameters\/eraps\n\n# In a running guest: verify the larger RSB is accessible\ndmesg | grep -i \"rsb\\|eraps\\|return stack\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A final note on terminology. You will see ERAPS described loosely as &#8220;RSB or return-address-predictor protection.&#8221; This is directionally correct but incomplete. ERAPS is not only protection. It is the recovery of virtualization performance that was lost to SpectreRSB mitigations \u2014 delivered as a hardware feature on Zen 5, now accessible to guest VMs on Linux 7.0. If you are sizing a new EPYC virtualization fleet, the performance implication is the headline, not the security flag.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"mldsa\">The Post-Quantum Story: ML-DSA Arrives in the Kernel <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The post-quantum cryptography transition is one of the most significant long-term changes happening to the global software supply chain, and almost nobody outside of cryptography circles is paying adequate attention.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The situation in brief. <strong>RSA and ECDSA<\/strong>, the classical signature algorithms that secure essentially all current code signing, TLS certificates, SSH host authentication, and kernel module signing, are vulnerable to <strong>Shor&#8217;s algorithm<\/strong> \u2014 an efficient quantum algorithm for factoring integers and computing discrete logarithms. A sufficiently large quantum computer running Shor&#8217;s algorithm can forge RSA and ECDSA signatures. No such computer exists today. Credible ones may exist in ten to fifteen years. Migrating a global cryptographic infrastructure takes ten to fifteen years. The math is tight.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>NIST&#8217;s response<\/strong> has been the post-quantum cryptography standardization process, which in August 2024 finalized three standards: <strong>ML-KEM<\/strong> (key encapsulation), <strong>ML-DSA<\/strong> (digital signatures), and <strong>SLH-DSA<\/strong> (stateless hash-based signatures). ML-DSA is based on <strong>Module Learning With Errors (MLWE)<\/strong> \u2014 a lattice problem for which no efficient quantum algorithm is known.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Linux 7.0 adds support for ML-DSA as a valid signature scheme for <strong>kernel module authentication<\/strong>. And \u2014 just as importantly \u2014 it <strong>removes support for SHA-1-based module signing<\/strong>. SHA-1 has been practically broken for years; its removal from the module signing pipeline is long overdue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For infrastructure teams operating locked-down secure-boot environments with custom kernel module signing pipelines, this is the most operationally significant security change in 7.0. If you maintain a signing pipeline, you need to evaluate your toolchain&#8217;s ML-DSA readiness and plan the migration before SHA-1-signed modules start failing to load.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practical workflow, assuming OpenSSL 3.3 or later with PQC support:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Generate an ML-DSA signing key pair\nopenssl genpkey -algorithm mldsa65 -out signing_key.pem\nopenssl req -new -x509 -key signing_key.pem -out signing_cert.pem \\\n  -days 3650 -subj \"\/CN=My Kernel Module Signing Key\/\"\n\n# Sign a kernel module\n\/usr\/lib\/linux-kbuild-7.0\/scripts\/sign-file \\\n  mldsa65 signing_key.pem signing_cert.pem my_module.ko\n\n# Verify the signature is attached\nmodinfo my_module.ko | grep -i sig<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Configuring a 7.0 kernel build to use ML-DSA by default:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>scripts\/config --enable CONFIG_MODULE_SIG\nscripts\/config --enable CONFIG_MODULE_SIG_ALL\nscripts\/config --set-str CONFIG_MODULE_SIG_HASH \"mldsa65\"\nscripts\/config --disable CONFIG_MODULE_SIG_SHA1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is an early, narrow adoption of post-quantum cryptography in a critical piece of infrastructure. TLS will follow. SSH host keys will follow. Web PKI will follow. Each of these migrations will take years. The kernel module signing migration in Linux 7.0 is a small, concrete proof point that the tooling is ready \u2014 and that anyone waiting to start their own migration is already behind schedule.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"heritage\">The Heritage Story: SPARC and Alpha Still Alive <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Tucked into the 7.0 merge window, Phoronix noticed something that reads almost like a geological entry: patches for <strong>Sun\/Oracle SPARC<\/strong> and <strong>DEC Alpha<\/strong> processors. In the same release cycle that stabilizes Rust and introduces post-quantum cryptography, the Linux kernel also fixed a user-space corruption bug during memory compaction on Alpha and added <code>clone3<\/code> syscall support to SPARC.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SPARC is a RISC architecture originally developed by Sun Microsystems and inherited by Oracle in 2010. DEC Alpha was Digital Equipment Corporation&#8217;s remarkable 64-bit RISC architecture from the 1990s \u2014 genuinely ahead of its time, discontinued in 2001 when Compaq shut down the line. Both architectures are decades past their mainstream relevance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And yet the Linux kernel continues to support them. Not perfunctorily. Actively. Patches reviewed and merged within the standard maintenance process, by people who care enough to do the work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is worth pausing on, because it illustrates something that is easy to miss in the usual feature-count coverage of kernel releases. <strong>The Linux kernel&#8217;s commitment to architectural breadth is not sentimentality.<\/strong> It reflects three realities that matter to anyone who thinks seriously about infrastructure:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Legacy systems exist in production.<\/strong> SPARC hardware still runs specific financial and governmental workloads where replacement cycles are measured in decades, not quarters. Without continued kernel support, these environments face a choice between unsupported software stacks and catastrophically expensive hardware migrations. The kernel keeping SPARC alive is the difference between &#8220;maintainable&#8221; and &#8220;stranded.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Architectural diversity is a forcing function for good code.<\/strong> Code that must compile and run correctly on SPARC, Alpha, x86_64, ARM64, RISC-V, and LoongArch simultaneously is structurally forced to respect architecture-neutral abstractions. It cannot casually assume x86 memory ordering, x86 page sizes, or x86 anything. This makes the codebase more portable and more honest than it would be if it optimized exclusively for the dominant architecture of the moment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Hardware preservation is real work.<\/strong> DEC Alpha systems are actively used by computer-architecture research groups and hardware-preservation communities. A working Linux port is the difference between a research platform and a museum piece.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of this is exciting in a headline sense. All of it is the kind of patient, quiet, uncelebrated maintenance that keeps the broader ecosystem trustworthy.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"conclusion\">What This Release Actually Means <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">There is a particular temptation, when writing about Linux kernel releases, to treat them as product launches. Feature lists. Comparison tables. Marketing-adjacent narratives about &#8220;what&#8217;s new&#8221; and &#8220;why you should upgrade.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is the wrong frame. Linux kernel releases are not products. They are <strong>dispatches from a forty-year engineering project that millions of us depend on<\/strong>, most of the time without thinking about it. The measure of a kernel release is not how exciting it is. The measure is whether it keeps the system trustworthy for the next twenty years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By that measure, Linux 7.0 is a remarkable release. <strong>Rust&#8217;s graduation<\/strong> means that memory-unsafe driver categories now have a credible alternative path. <strong>XFS self-healing<\/strong> means that the most common enterprise Linux filesystem has a meaningfully better failure mode. <strong>ERAPS virtualization<\/strong> means that the hardware industry has finally started paying back the performance tax that speculative-execution mitigations imposed. <strong>ML-DSA signatures<\/strong> mean that the kernel module signing pipeline is among the first critical pieces of infrastructure to begin the post-quantum migration \u2014 quietly, correctly, ahead of schedule. And <strong>the continued maintenance of SPARC and Alpha<\/strong> is a quiet reminder of what the project&#8217;s commitments actually are.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of this will appear in a marketing deck. All of this will shape what infrastructure looks like in 2040.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For anyone running a kernel-forward distribution, the upgrade path is easy: <strong>Ubuntu 26.04 LTS &#8220;Resolute Raccoon&#8221;<\/strong> and <strong>Fedora 44<\/strong> both ship 7.0 as their default kernel. For everyone else \u2014 if you have reason to build your own, or to test specific configurations before distribution packages land \u2014 the source is at kernel.org, the GPG signatures are published, and a full build from a clean checkout on a modern workstation takes roughly ten minutes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wget https:\/\/cdn.kernel.org\/pub\/linux\/kernel\/v7.x\/linux-7.0.tar.xz\nwget https:\/\/cdn.kernel.org\/pub\/linux\/kernel\/v7.x\/linux-7.0.tar.sign\nunxz linux-7.0.tar.xz\ngpg --verify linux-7.0.tar.sign linux-7.0.tar   # always verify signatures\ntar -xf linux-7.0.tar &amp;&amp; cd linux-7.0\n\ncp \/boot\/config-$(uname -r) .config              # start from known-good\nmake olddefconfig\ntime make -j$(nproc) LOCALVERSION=\"-custom\"\n\nsudo make modules_install\nsudo make install\nsudo update-grub                                 # or grub2-mkconfig on RHEL<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The open-source model continues to deliver what no proprietary alternative can: transparency, auditability, architectural breadth, and the patient maturation of engineering investments over multi-year timescales. Linux 7.0 is not a revolution. It is the slow, persistent, boring revolution \u2014 the only kind that actually lasts.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>While the industry chases the next AI benchmark and the next model announcement, something genuinely important happened on April 12, 2026, and it arrived with almost no fanfare: Linus Torvalds released Linux kernel 7.0. The announcement was accompanied by a typically deadpan Torvalds joke \u2014 he bumped the major version, he said, because 6.19 was [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[51,48,47,54,43,46,20,50,52,49,44,55,56,45,53],"class_list":["post-278","post","type-post","status-publish","format-standard","hentry","category-opensource","tag-alpha","tag-amd","tag-epyc","tag-infrastructure","tag-kernel","tag-kvm","tag-linux-2","tag-ml-dsa","tag-open-source","tag-post-quantum","tag-rust","tag-security","tag-sparc","tag-xfs","tag-zen5"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/marcoferrigno.net\/it\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer\" \/>\n<meta property=\"og:description\" content=\"While the industry chases the next AI benchmark and the next model announcement, something genuinely important happened on April 12, 2026, and it arrived with almost no fanfare: Linus Torvalds released Linux kernel 7.0. The announcement was accompanied by a typically deadpan Torvalds joke \u2014 he bumped the major version, he said, because 6.19 was [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/marcoferrigno.net\/it\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/\" \/>\n<meta property=\"og:site_name\" content=\"Marco Ferrigno | IT System Engineer\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-30T06:47:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-30T06:47:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"marcoferrigno\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Scritto da\" \/>\n\t<meta name=\"twitter:data1\" content=\"marcoferrigno\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/\"},\"author\":{\"name\":\"marcoferrigno\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/#\\\/schema\\\/person\\\/7c68a429c25640e509b5ff667078d1f2\"},\"headline\":\"Linux Kernel 7.0: The Quiet Revolution That Changes Everything\",\"datePublished\":\"2026-04-30T06:47:20+00:00\",\"dateModified\":\"2026-04-30T06:47:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/\"},\"wordCount\":2555,\"image\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/marcoferrigno.net\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/linux-7.0-cover-post-v2-1024x576.png\",\"keywords\":[\"alpha\",\"amd\",\"epyc\",\"infrastructure\",\"kernel\",\"kvm\",\"linux\",\"ml-dsa\",\"open-source\",\"post-quantum\",\"rust\",\"security\",\"sparc\",\"xfs\",\"zen5\"],\"articleSection\":[\"opensource\"],\"inLanguage\":\"it-IT\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/\",\"url\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/\",\"name\":\"Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/marcoferrigno.net\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/linux-7.0-cover-post-v2-1024x576.png\",\"datePublished\":\"2026-04-30T06:47:20+00:00\",\"dateModified\":\"2026-04-30T06:47:24+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/#\\\/schema\\\/person\\\/7c68a429c25640e509b5ff667078d1f2\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#primaryimage\",\"url\":\"https:\\\/\\\/marcoferrigno.net\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/linux-7.0-cover-post-v2-1024x576.png\",\"contentUrl\":\"https:\\\/\\\/marcoferrigno.net\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/linux-7.0-cover-post-v2-1024x576.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/marcoferrigno.net\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Linux Kernel 7.0: The Quiet Revolution That Changes Everything\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/#website\",\"url\":\"https:\\\/\\\/marcoferrigno.net\\\/\",\"name\":\"Marco Ferrigno | IT System Engineer\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/marcoferrigno.net\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/marcoferrigno.net\\\/#\\\/schema\\\/person\\\/7c68a429c25640e509b5ff667078d1f2\",\"name\":\"marcoferrigno\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g\",\"caption\":\"marcoferrigno\"},\"sameAs\":[\"https:\\\/\\\/marcoferrigno.net\"],\"url\":\"https:\\\/\\\/marcoferrigno.net\\\/it\\\/author\\\/marcoferrigno\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/marcoferrigno.net\/it\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/","og_locale":"it_IT","og_type":"article","og_title":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer","og_description":"While the industry chases the next AI benchmark and the next model announcement, something genuinely important happened on April 12, 2026, and it arrived with almost no fanfare: Linus Torvalds released Linux kernel 7.0. The announcement was accompanied by a typically deadpan Torvalds joke \u2014 he bumped the major version, he said, because 6.19 was [&hellip;]","og_url":"https:\/\/marcoferrigno.net\/it\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/","og_site_name":"Marco Ferrigno | IT System Engineer","article_published_time":"2026-04-30T06:47:20+00:00","article_modified_time":"2026-04-30T06:47:24+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2.png","type":"image\/png"}],"author":"marcoferrigno","twitter_card":"summary_large_image","twitter_misc":{"Scritto da":"marcoferrigno","Tempo di lettura stimato":"12 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#article","isPartOf":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/"},"author":{"name":"marcoferrigno","@id":"https:\/\/marcoferrigno.net\/#\/schema\/person\/7c68a429c25640e509b5ff667078d1f2"},"headline":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything","datePublished":"2026-04-30T06:47:20+00:00","dateModified":"2026-04-30T06:47:24+00:00","mainEntityOfPage":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/"},"wordCount":2555,"image":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#primaryimage"},"thumbnailUrl":"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png","keywords":["alpha","amd","epyc","infrastructure","kernel","kvm","linux","ml-dsa","open-source","post-quantum","rust","security","sparc","xfs","zen5"],"articleSection":["opensource"],"inLanguage":"it-IT"},{"@type":"WebPage","@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/","url":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/","name":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything - Marco Ferrigno | IT System Engineer","isPartOf":{"@id":"https:\/\/marcoferrigno.net\/#website"},"primaryImageOfPage":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#primaryimage"},"image":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#primaryimage"},"thumbnailUrl":"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png","datePublished":"2026-04-30T06:47:20+00:00","dateModified":"2026-04-30T06:47:24+00:00","author":{"@id":"https:\/\/marcoferrigno.net\/#\/schema\/person\/7c68a429c25640e509b5ff667078d1f2"},"breadcrumb":{"@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#primaryimage","url":"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png","contentUrl":"https:\/\/marcoferrigno.net\/wp-content\/uploads\/2026\/04\/linux-7.0-cover-post-v2-1024x576.png"},{"@type":"BreadcrumbList","@id":"https:\/\/marcoferrigno.net\/linux-kernel-7-0-the-quiet-revolution-that-changes-everything\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/marcoferrigno.net\/"},{"@type":"ListItem","position":2,"name":"Linux Kernel 7.0: The Quiet Revolution That Changes Everything"}]},{"@type":"WebSite","@id":"https:\/\/marcoferrigno.net\/#website","url":"https:\/\/marcoferrigno.net\/","name":"Marco Ferrigno | IT System Engineer","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/marcoferrigno.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"it-IT"},{"@type":"Person","@id":"https:\/\/marcoferrigno.net\/#\/schema\/person\/7c68a429c25640e509b5ff667078d1f2","name":"marcoferrigno","image":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/secure.gravatar.com\/avatar\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/caabe5659f19693efc6f0b16630c81be039df9cedd16a3edd5bf688266d31508?s=96&d=mm&r=g","caption":"marcoferrigno"},"sameAs":["https:\/\/marcoferrigno.net"],"url":"https:\/\/marcoferrigno.net\/it\/author\/marcoferrigno\/"}]}},"_links":{"self":[{"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/posts\/278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/comments?post=278"}],"version-history":[{"count":5,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/posts\/278\/revisions"}],"predecessor-version":[{"id":294,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/posts\/278\/revisions\/294"}],"wp:attachment":[{"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/media?parent=278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/categories?post=278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/marcoferrigno.net\/it\/wp-json\/wp\/v2\/tags?post=278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}