PullSec's Note

In my previous kernel exploitation notes, I mostly focused on memory corruption vulnerabilities such as Use-After-Free, along with the general workflow behind building exploitation chains.

CVE-2026-31431, also known as Copy Fail, is different.

In my previous kernel exploitation notes, I mostly focused on vulnerabilities that expose powerful primitives such as arbitrary read or write.

CVE-2022-32250 is different.

In this post, I’m trying to build a solid understanding of how the Linux kernel works from an exploitation perspective.

The goal is not to cover everything, but to get a clear picture of how things are structured before diving into real vulnerabilities.

In this part, we move from observation to interaction.

The previous post focused on building a controlled wireless lab.
Now, we use that lab to understand why WEP is considered broken.

In this part, we move from theory to practice.

In the first part, the goal was to understand how Wi-Fi works from a security perspective.
Now, the goal is different: interacting with it in a controlled way.

Before performing any wireless experiments, we need a lab where everything is predictable, observable, and safe to break.

In this post, I’m trying to build a clear foundation for understanding how Wi-Fi works from a security perspective.

The goal is not to cover every wireless concept, but to understand the pieces that matter before moving into practical labs.