<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research on Prepakis Georgios | Kernelstub | Security Researcher</title><link>https://blog.kernelstub.dev/tags/research/</link><description>Recent content in Research on Prepakis Georgios | Kernelstub | Security Researcher</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 06 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kernelstub.dev/tags/research/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse Engineering a 2012 Toyota Yaris: From OBD-II to Exploit Chain</title><link>https://blog.kernelstub.dev/posts/reverse-engineering-a-2012-toyota-yaris-from-obd-ii-to-exploit-chain/</link><pubDate>Fri, 06 Feb 2026 00:00:00 +0000</pubDate><guid>https://blog.kernelstub.dev/posts/reverse-engineering-a-2012-toyota-yaris-from-obd-ii-to-exploit-chain/</guid><description>&lt;h2 id="chapter-1-introduction-and-laboratory-setup"&gt;Chapter 1: Introduction and Laboratory Setup&lt;/h2&gt;
&lt;p&gt;I picked a 2012 Toyota Yaris for this project mostly because of what it isn&amp;rsquo;t: it&amp;rsquo;s not a flagship, it&amp;rsquo;s not loaded with the kind of aftermarket telematics and OTA update infrastructure that makes modern vehicles a moving target for remote attacks, and it&amp;rsquo;s cheap enough on the used market that I could buy one, break it, and not lose sleep over it. That&amp;rsquo;s actually the point. Cars like this one make up a huge chunk of the vehicles still on the road today, and the electronics inside them were designed in an era when &amp;ldquo;attack surface&amp;rdquo; mostly meant &amp;ldquo;whoever plugs a scan tool into the OBD-II port at a dealership.&amp;rdquo; Nobody was thinking about buffer overflows delivered over a CAN frame. That assumption, it turns out, ages badly, and this post walks through exactly how badly.&lt;/p&gt;</description></item><item><title>From Bits to Breaks A Low Level System Exploitation and Defense</title><link>https://blog.kernelstub.dev/posts/from-bits-to-breaks-a-low-level-system-exploitation-and-defense/</link><pubDate>Sat, 25 Oct 2025 00:00:00 +0000</pubDate><guid>https://blog.kernelstub.dev/posts/from-bits-to-breaks-a-low-level-system-exploitation-and-defense/</guid><description>&lt;h2 id="introduction-and-scope"&gt;Introduction and Scope&lt;/h2&gt;
&lt;p&gt;Here&amp;rsquo;s the core question driving this whole project: how do software and hardware actually interact once you strip away the abstraction layers that normally hide the messy details from you? Compilers, operating systems, and runtimes exist precisely so you can forget about page tables, cache lines, and instruction pipelines while you get work done. Attackers, and the researchers trying to stay ahead of them, don&amp;rsquo;t get that luxury. Every exploit involving memory corruption, firmware, or a leaky microarchitectural feature lives exactly at that seam between the code you wrote and the silicon actually running it. This research examines that seam systematically, aiming to produce techniques reproducible enough to be useful, rigorous enough to be academically sound, and constrained enough to stay ethically defensible.&lt;/p&gt;</description></item></channel></rss>