Hello OP here
I was one of the 1100 people impacted by the recent layoff. Thats when I started looking into offensive security/exploit writing more closely and actively. I have been doing blue teaming/defender's work for over a decade. While I knew about and had explored exploit writing, I had never done it as my day job (mostly for fun and CTF events). As I had no job and some downtime, I started looking into it.
My aim is always to write in a way that people without much hands on experience with exploit dev can still understand and learn from.
Feel free to share your questions/comments or ways I can make these blogs even more reader/beginner friendly.
m happy to answer any technical questions, though I believe HN folks know much more than I do about the Linux kernel.
Hello OP here I was one of the 1100 people impacted by the recent layoff. Thats when I started looking into offensive security/exploit writing more closely and actively. I have been doing blue teaming/defender's work for over a decade. While I knew about and had explored exploit writing, I had never done it as my day job (mostly for fun and CTF events). As I had no job and some downtime, I started looking into it.
My 1st blog post was about a V8 exploit: https://blog.himanshuanand.com/2026/08/i-had-some-free-time-... This is the 2nd one, about kernel exploitation.
My aim is always to write in a way that people without much hands on experience with exploit dev can still understand and learn from. Feel free to share your questions/comments or ways I can make these blogs even more reader/beginner friendly. m happy to answer any technical questions, though I believe HN folks know much more than I do about the Linux kernel.