<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rootless on The Coders Blog</title><link>https://thecodersblog.com/tag/rootless/</link><description>Recent content in Rootless on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 May 2026 15:09:57 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/rootless/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Alert: CVE-2026-31431 Exposes Rootless Containers to 'Copy Fail'</title><link>https://thecodersblog.com/cve-2026-31431-copy-fail-vs-rootless-containers-2026/</link><pubDate>Tue, 05 May 2026 15:09:57 +0000</pubDate><guid>https://thecodersblog.com/cve-2026-31431-copy-fail-vs-rootless-containers-2026/</guid><description>&lt;p&gt;Imagine a world where an unprivileged process, with no special rights, can reach into the kernel&amp;rsquo;s memory and alter critical system components. This isn&amp;rsquo;t science fiction; it&amp;rsquo;s the reality introduced by CVE-2026-31431, affectionately (and terrifyingly) dubbed &amp;ldquo;Copy Fail.&amp;rdquo; For those operating in the containerized world, especially with rootless setups, this vulnerability is a stark reminder that even seemingly robust isolation mechanisms can have hidden pathways to compromise.&lt;/p&gt;
&lt;h3 id="the-core-problem-kernel-memory-corruption-via-af_alg"&gt;The Core Problem: Kernel Memory Corruption via &lt;code&gt;AF_ALG&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;CVE-2026-31431 is a high-severity local privilege escalation (LPE) vulnerability residing within the Linux kernel&amp;rsquo;s cryptographic subsystem, specifically the &lt;code&gt;AF_ALG&lt;/code&gt; (userspace crypto API). The flaw lies in a logic error within the &lt;code&gt;algif_aead&lt;/code&gt; module. At its heart, the exploit leverages the &lt;code&gt;splice()&lt;/code&gt; system call to perform controlled, 4-byte writes into the kernel&amp;rsquo;s shared page cache. This seemingly small manipulation is enough to corrupt in-memory copies of critical setuid binaries, such as &lt;code&gt;/usr/bin/su&lt;/code&gt;. The ultimate consequence? An unprivileged user can execute a corrupted setuid binary and gain root privileges.&lt;/p&gt;</description></item></channel></rss>