← All talks

Kernel Drivers: The Power Within #shorts

BSides Frankfurt1:14151 viewsPublished 2026-01Watch on YouTube ↗
About this talk
Explore kernel driver structure and their potential risks. Sending packages with defined structures is key, but errors can linger until reboot. Understand the power—and responsibility—of kernel-level access. #BsidesFrankfurt #Bsides #BsidesFra #JuanSacco
Show transcript [en]

is this is the structure that we're going to use to communicate. So basically we send a package and then that package needs to have a structure. You define the structure that the package is going to have right and then this is the structure for that IOCL. You cannot just leave it there because it will not nothing in the kernel we there is no garbage collector. There is nothing like that. So if you make an error it will remain there until you reboot the machine. Right? So that's I mention it because of the driver download. Some drivers they don't have driver unload and then what's going to happen the driver just remain there until yeah there's no way to uh unload

it unless you use another driver. So now that you have a little bit more understanding on how ex uh drivers works and remember um whatever you can do on kernel you can that's why it's rootkit development because you can make a the same you can make a software driver and then have that power from the kernel and ask a user or application to do whatever you wanted from it right um and you will see some examples from it. But uh think of what you can do from the kernel if you have kernel power.