> For the complete documentation index, see [llms.txt](https://spikysabra.gitbook.io/kernelcactus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spikysabra.gitbook.io/kernelcactus/pocs/intro.md).

# Intro

So far, we have made it clear that the basic structures of the windows kernel, as undocumented as they are, can still be understood with some effort to connect all the pointers between the different objects.

Furthermore, we have made it clear that in order to navigate through the kernel, all we need to do is to combine our knowledge of the relationships between structs, and our ability to read/write the kernel memory.

With the said knowledge and basic navigation system, it is now time to weaponize what we know in order to create killer scenarios which will demonstrate just how explosive and dangerous exploitation of this vulnerability is.

Keep in mind, the POCs you are about to be introduced to, are not claiming to be all there is to it, rather then an extended view of how one can develop further exploits and malicious functionalities on top of our already existing knowledge. We are well aware that there is much more to be done.

<figure><img src="/files/Pv08vgwqiFncvKoGQVXA" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://spikysabra.gitbook.io/kernelcactus/pocs/intro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.