Linux Dirty Frag Kernel Privilege Escalation
Description
The following analytic detects exploitation of Dirty Frag (CVE-2026-43284 and CVE-2026-43500), a Linux kernel local privilege escalation vulnerability. The exploit corrupts the kernel page cache via the IPsec ESP or RxRPC subsystems using a high-frequency splice() syscall loop, followed by a privilege transition to root in the same audit session. This analytic anchors on the exploit-specific behavioral signature, a sustained splice() spray (50 or more calls within a 60-second window) from an unprivileged process executing from a user-writable path (/home, /tmp, /dev/shm, /var/tmp, /run/user, /root), followed within 5 minutes by execution of a set-uid binary in the same auditd session.
Query · spl
`linux_auditd`
type=SYSCALL
key=splice_user
exe IN (
"/home/*",
"/tmp/*",
"/var/tmp/*",
"/dev/shm/*",
"/run/user/*",
"/root/*"
)
| bin _time span=60s
| eval user = coalesce(user, auid, AUID)
| stats count AS splice_count
values(exe) AS spray_binary
values(pid) AS spray_pid
values(user) AS user
earliest(_time) AS spray_start
latest(_time) AS spray_end
BY auid host ses _time
| where splice_count >= 50
| join type=inner auid host ses [
search `linux_auditd`
type=SYSCALL
key=process_creation
exe IN (
"/usr/bin/chfn",
"/usr/bin/chsh",
"/usr/bin/fusermount3",
"/usr/bin/gpasswd",
"/usr/bin/mount",
"/usr/bin/newgrp",
"/usr/bin/passwd",
"/usr/bin/su",
"/usr/bin/sudo",
"/usr/bin/umount",
"/usr/lib/dbus-1.0/dbus-daemon-launch-helper",
"/usr/lib/landscape/apt-update",
"/usr/lib/openssh/ssh-keysign",
"/usr/lib/polkit-1/polkit-agent-helper-1"
)
| stats earliest(_time) AS privesc_time
values(exe) AS privesc_binary
values(comm) AS privesc_comm
values(ppid) AS privesc_ppid
BY auid host ses
]
| eval window_secs = privesc_time - spray_end
| where window_secs >= 0 AND window_secs <= 300
| `security_content_ctime(spray_start)`
| `security_content_ctime(spray_end)`
| `security_content_ctime(privesc_time)`
| rename host AS dest
| table dest user auid ses spray_binary spray_pid
splice_count spray_start spray_end privesc_binary
privesc_comm privesc_ppid privesc_time window_secs
| `linux_dirty_frag_kernel_privilege_escalation_filter`
Implementation guide
This analytic requires Linux auditd telemetry forwarded to Splunk via the Splunk_TA_nix add-on with the linux_audit sourcetype (referenced through the linux_auditd macro).
The detection depends on two audit rule keys, both of which are standard in the Neo23x0 recommended ruleset (https://github.com/Neo23x0/auditd) and the existing ESCU Copy Fail analytic (Linux Auditd Copy Fail Privilege Escalation), so no detection-specific custom keys are introduced.
PREREQUISITE 1; splice_user key.
-a always,exit -F arch=b64 -S splice -S vmsplice -F success=1 -F auid>=1000 -F auid!=unset -k splice_user -a always,exit -F arch=b32 -S splice -S vmsplice -F success=1 -F auid>=1000 -F auid!=unset -k splice_user
Operators should baseline splice volume in their environment before enabling. Hosts running heavy zero-copy I/O workloads (specific: web servers, mail transfer agents, container runtimes) may need additional filtering.
PREREQUISITE 2; process_creation key.
-a always,exit -F arch=b64 -S execve -S execveat -F auid>=1000 -F auid!=unset -k process_creation -a always,exit -F arch=b32 -S execve -S execveat -F auid>=1000 -F auid!=unset -k process_creation
Known false positives
- The splice volume threshold (50 calls per 60 seconds from a single process in a user-writable path) is calibrated against the V4bel public PoC, which produces 100-460 splice calls in 90 seconds depending on system state. Legitimate user-mode workloads that may produce splice() calls (web servers, mail transfer agents, language runtimes) typically execute from system paths (/usr/sbin, /usr/bin, /usr/lib) and are excluded by the user-writable path filter. Custom-compiled applications, developer test binaries, or container runtimes executing from /home or /tmp could theoretically reach the volume threshold during legitimate I/O-heavy workloads (large file copies, log rotation, archive operations). Operators should baseline splice volume in their environment before enabling as a notable event. If false positives occur, add an allowlist of trusted binary paths via the linux_dirty_frag_kernel_privilege_escalation_filter macro, or raise the splice_count threshold based on observed legitimate-workload baseline.
Analyst notes
Known false positives: The splice volume threshold (50 calls per 60 seconds from a single process in a user-writable path) is calibrated against the V4bel public PoC, which produces 100-460 splice calls in 90 seconds depending on system state. Legitimate user-mode workloads that may produce splice() calls (web servers, mail transfer agents, language runtimes) typically execute from system paths (/usr/sbin, /usr/bin, /usr/lib) and are excluded by the user-writable path filter. Custom-compiled applications, developer test binaries, or container runtimes executing from /home or /tmp could theoretically reach the volume threshold during legitimate I/O-heavy workloads (large file copies, log rotation, archive operations). Operators should baseline splice volume in their environment before enabling as a notable event. If false positives occur, add an allowlist of trusted binary paths via the linux_dirty_frag_kernel_privilege_escalation_filter macro, or raise the splice_count threshold based on observed legitimate-workload baseline.