<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit on Moe's VR blog</title><link>https://mohandacherir.github.io/Qdiv7/tags/exploit/</link><description>Recent content in Exploit on Moe's VR blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mohandacherir.github.io/Qdiv7/tags/exploit/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-31419: Use-After-Free in the Linux Bonding Driver</title><link>https://mohandacherir.github.io/Qdiv7/posts/cve-2026-31419/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://mohandacherir.github.io/Qdiv7/posts/cve-2026-31419/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Linux offers a way to synchronize multiple network interfaces, physical or virtual, and make them run a single logical NIC. The bonding driver handles of all that work.
It is present in all major distros and this bug is exploitable in the ones that allow usernamespaces for unprivileged users like in RedHat or Fedora; that is, it&amp;rsquo;s reachable from any code path that can send packets out of the bonding device.&lt;/p></description></item><item><title>Notes on io_uring bugs &amp; exploitation</title><link>https://mohandacherir.github.io/Qdiv7/posts/io_uring_exploitation/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://mohandacherir.github.io/Qdiv7/posts/io_uring_exploitation/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>&lt;code>io_uring&lt;/code> is one of the most ambitious kernel interfaces added in recent years: a shared-memory asynchronous I/O engine designed to avoid the syscall-heavy overhead of traditional &lt;code>read&lt;/code>, &lt;code>write&lt;/code>, and networking paths. That performance-oriented design also makes it unusually interesting from a security perspective, because the subsystem is full of long-lived shared state, lifetime-sensitive objects, and fast paths that interact closely with core kernel memory-management code.&lt;/p></description></item></channel></rss>