kernelCTF: add CVE-2026-53361_lts - #416
Conversation
8f7584a to
22a2b68
Compare
|
This mostly looks good but could you go into a bit more detail in your exploit.md? It's only one line right now. It doesn't need to be very long, just a bit more than a single line :) |
|
Hey @matrizzo! Thanks for the review. I have added the documentation. |
| /* ── Setup helpers ────────────────────────────────────────────────── */ | ||
|
|
||
| static Target prepare_kernelxdk() { | ||
| Target target("kernelctf", "local"); |
There was a problem hiding this comment.
Please check https://xdk.dev/libxdk/sample_exploit.html and https://github.com/google/kernel-research/tree/main/libxdk/samples on how Target should be defined and used.
The first link also shows how missing structures, symbols could be added to specific target that your exploit is written for.
| setrlimit(RLIMIT_NOFILE, &rl); | ||
| } | ||
|
|
||
| struct kernel_pipe_buffer { |
There was a problem hiding this comment.
target.AddStruct should be used for that. Please check https://xdk.dev/libxdk/sample_exploit.html
| // @step(name="Exploit attempt (forked)") | ||
| pid_t pid = fork(); | ||
| if (pid == 0) { | ||
| pin_to_cpu(0); |
There was a problem hiding this comment.
| write(ctx->krw_pipe[1], &new_mode, sizeof(new_mode)); | ||
| } | ||
|
|
||
| int main() { |
There was a problem hiding this comment.
You should also implement --vuln-trigger. Please check https://github.com/google/security-research/blob/88ec1d535b0d147eec404751f0457e7162450aed/kernelctf/rules.md#exploit
artmetla
left a comment
artmetla
left a comment
There was a problem hiding this comment.
@sysroot314 Please check my comments on kernelXDK usage and fix / comment on why it's not applicable in this case.
3 participants
No description provided.