<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GNU on The Coders Blog</title><link>https://thecodersblog.com/tag/gnu/</link><description>Recent content in GNU on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 03:29:07 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/gnu/index.xml" rel="self" type="application/rss+xml"/><item><title>GNU IFUNC: The Real Culprit Behind CVE-2024-3094</title><link>https://thecodersblog.com/gnu-ifunc-s-role-in-cve-2024-3094-2026/</link><pubDate>Fri, 08 May 2026 03:29:07 +0000</pubDate><guid>https://thecodersblog.com/gnu-ifunc-s-role-in-cve-2024-3094-2026/</guid><description>&lt;p&gt;The recent XZ Utils backdoor (CVE-2024-3094) sent shockwaves through the Linux ecosystem. While much attention has rightfully focused on the insidious nature of the attack and its supply-chain vector, the underlying mechanism that facilitated its stealthiest payloads has been largely overlooked: &lt;strong&gt;GNU&amp;rsquo;s Indirect Function (IFUNC)&lt;/strong&gt;. This feature, buried within &lt;code&gt;glibc&lt;/code&gt;, was not merely an incidental detail; it was the very linchpin that enabled the backdoor&amp;rsquo;s most potent functionality – covert function hijacking at runtime.&lt;/p&gt;</description></item></channel></rss>