An integer overflow vulnerability exists in the sys_epoll_wait function in eventpoll.c in the Linux kernel versions 2.6 through 2.6.11. The flaw allows a local user to trigger an integer overflow by passing a large number of events to sys_epoll_wait, resulting in the ability to overwrite kernel memory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This six-file repository archives two historical Linux kernel local exploit implementations, with per-CVE README files and a top-level index. CVE-2005-0736/1397.c is a standalone C exploit for the sys_epoll_wait integer-overflow condition on Linux 2.6.5-2.6.11. It detects CPU capabilities via /proc/cpuinfo, accepts PAE/PSE, page-allocation, exploit-path, and thread-stack-size tuning options, modifies low kernel memory/IDT state, and attempts to obtain a root /bin/sh shell. CVE-2005-1263/25647.sh is a Bash wrapper that emits, compiles, and runs two i386 C programs plus a custom linker script to construct a malformed ELF and repeatedly induce coredumps, warning that it can crash the host. The latter is a destructive trigger PoC and does not include a reliable post-exploitation root-shell payload. No exploit framework or network communications are present; URLs are documentary references only.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.