
Local privilege escalation PoC for CVE-2026-74469, exploiting an SCTP diagnostic-reply kernel memory corruption to gain root on Linux x86-64 systems.
[!WARNING] The PoC is provided solely to help defenders, maintainers, and authorized security teams validate patches, mitigations, detections, and exposure on systems they own or are explicitly authorized to test.
You are solely responsible for ensuring that your use of this material is lawful, authorized, controlled, and conducted in an isolated test environment.
[!WARNING] This PoC is destructive. It overwrites roughly 8 MiB of kernel memory and leaves corrupted page tables held by the
diagspill_holdsacrificial-memory holder until reboot. Killing that process can destabilize the kernel.Unrelated memory may be corrupted and the machine may panic. Run only in a disposable VM/throwaway host.
The PoC:
sudo, and detaches the process
holding the corrupted mappings.The PoC assumes and targets x86-64 to keep things simple. In theory, the bug should not be arch-specific.
Enumerating exhaustively for completeness:
6.17.0-35-generic, or Fedora 44 with
6.19.10-300.fc44.x86_64 (you can try removing these checks, but other
distros/kernel versions may require per-target customization/grooming)MemTotal between 3,700,000 and 4,200,000 KiB_, or -/root or passwordless sudosctp_diag kernel support, transparent huge-page allocation, enough
process/file limits for 2,048 workers and the diagnostic socket wall, and
enough x86-64 address space and memory to retain about 2,343 MiB of page
tables on Ubuntu or 3,125 MiB on Fedora/etc/sudoers.d include and an executable /usr/bin/sudo/usr/bin/env, cc with libc and Linux UAPI
development headers, , , , , and The PoC is very vCPU-count-/RAM-sensitive, so it enforces 4 vCPUs and 4 GB RAM. You will likely need per-target customization/grooming for other vCPU/memory combos.
Run it as an unprivileged user with a passwd entry; the PoC can take a bit of
time to build the large SCTP association.
python3 diagspill_root_repro.py
After a run (successful or not), reboot the machine to release
diagspill_holdto be safe. If you kill it directly, you will almost certainly
destabilize the kernel.
idsudotrueshrm