<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kernel on Leandro&#39;s Code Cave</title>
    <link>https://iamleandrooooo.github.io/tags/kernel/</link>
    <description>Recent content in Kernel on Leandro&#39;s Code Cave</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iamleandrooooo.github.io/tags/kernel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Five Ghosts in Ring Zero - Autopsies of Windows Kernel Exploits That Vanished Under Proof</title>
      <link>https://iamleandrooooo.github.io/posts/five_ghosts_in_ring_zero/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://iamleandrooooo.github.io/posts/five_ghosts_in_ring_zero/</guid>
      <description>There is a version of vulnerability research that reads like archaeology with a kill chain at the end.&#xA;You find the unchecked multiply. You recover the IOCTL. You draw the structure. You name the primitive. You write the report. Microsoft assigns the case, the case becomes a CVE, and the write-up begins with the satisfying sentence:&#xA;I found a bug.&#xA;This is not that write-up.&#xA;This is about five times I found code that was absolutely wrong and a vulnerability that absolutely was not there.</description>
    </item>
    <item>
      <title>Refuting a condrv Kernel Read - Chasing a COMPLETE_IO memmove Through the Console IPC and a Self-Verifying PoC, Only to Lose to One Decompiler-Hidden ProbeForRead on Windows 11 24H2</title>
      <link>https://iamleandrooooo.github.io/posts/the-arbitrary-kernel-read-that-wasnt/</link>
      <pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://iamleandrooooo.github.io/posts/the-arbitrary-kernel-read-that-wasnt/</guid>
      <description>1. Why the console driver is an attack surface at all condrv.sys is the Console Driver. Since the Windows 7-era console rewrite (and especially post-Windows 10, when the console host moved out of csrss into conhost.exe), condrv is the kernel broker sitting between a console client (your cmd.exe, your powershell.exe - anything with a console) and a console server (conhost.exe). Every ReadConsole, WriteConsole, and the whole console-handle machinery is marshalled through it.</description>
    </item>
    <item>
      <title>The Sandbox Broker That Couldn&#39;t Be Confused - Forging an AppContainer Token to Reach bfs.sys and Failing to Path-Confuse a File Broker That Re-Runs the Access Check in the Caller&#39;s Own Context on Windows 11 24H2</title>
      <link>https://iamleandrooooo.github.io/posts/the-broker-that-rechecks-access/</link>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://iamleandrooooo.github.io/posts/the-broker-that-rechecks-access/</guid>
      <description>1. What a file broker is, and why it is a sandbox-escape target An AppContainer (or otherwise sandboxed) process cannot touch the filesystem directly - its token carries a restricted capability set, and the object manager denies it any FILE object outside that set. To do legitimate file work it has to ask a broker: a more-privileged component that performs the operation on the sandbox&amp;rsquo;s behalf and hands back the result.</description>
    </item>
  </channel>
</rss>
