CVE-2026-53362: Linux Kernel Unspecified Vulnerability (KEV) Exploitation Indicators
Detects host-level indicators consistent with exploitation of CVE-2026-53362, an unspecified Linux Kernel vulnerability listed on the CISA KEV catalog (BOD 26-04). Because the upstream fix spans multiple stable kernel commits and no public PoC or precise affected-version range is available, this detection focuses on behavioral signals of local kernel exploitation: unexpected privilege escalation to UID 0, kernel oops/BUG/taint messages coinciding with unprivileged process activity, suspicious loading of kernel modules, and abnormal syscall/capability abuse. Alerts are exposure-and-behavior signals, not proof of the specific bug; correlate with kernel version and patch state.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Linux
- Product
- Kernel
Timeline
- Disclosed
- August 27, 2026
References & Proof of Concept
- https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
- https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
- https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
- https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e
- https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-53362
CVSS
What is CVE-2026-53362 CVE-2026-53362: Linux Kernel Unspecified Vulnerability (KEV) Exploitation Indicators?
CVE-2026-53362: Linux Kernel Unspecified Vulnerability (KEV) Exploitation Indicators (CVE-2026-53362) maps to the Privilege Escalation and Execution tactics — the adversary is trying to gain higher-level permissions in MITRE ATT&CK.
This page provides production-ready detection logic for CVE-2026-53362: Linux Kernel Unspecified Vulnerability (KEV) Exploitation Indicators, covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, Linux Auditd via MDE. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Privilege Escalation Execution
let suspiciousParents = dynamic(["bash","sh","dash","zsh","python","python3","perl","nc","ncat"]);
DeviceProcessEvents
| where Timestamp > ago(1d)
| where AccountName == "root" or InitiatingProcessAccountName != "root"
| where InitiatingProcessAccountName != "root" and AccountName == "root"
| where InitiatingProcessFileName in~ (suspiciousParents)
| where ProcessCommandLine has_any ("id", "whoami", "/bin/sh", "setuid", "cap_setuid")
| project Timestamp, DeviceName, InitiatingProcessAccountName, InitiatingProcessFileName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine
| order by Timestamp desc Flags processes that transition from a non-root initiating account to a root-owned child spawned by an interactive shell or scripting interpreter — a common post-exploitation pattern for local kernel privilege escalation such as CVE-2026-53362.
Data Sources
Required Tables
False Positives
- Legitimate sudo/su elevation by administrators from interactive shells
- Configuration management agents (Ansible, Salt) escalating to root
- Container runtimes launching root processes from unprivileged supervisors
Sigma rule & cross-platform mapping
The detection logic for CVE-2026-53362: Linux Kernel Unspecified Vulnerability (KEV) Exploitation Indicators (CVE-2026-53362) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: process_creation
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-53362
References (9)
- https://nvd.nist.gov/vuln/detail/CVE-2026-53362
- https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
- https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
- https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
- https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e
- https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulated non-root to root process transition via setuid helper
Expected signal: Process launch of /tmp/rootshell with effective UID 0 initiated by user 'nobody'; auditd SYSCALL with euid=0 auid=nobody.
- Test 2Kernel taint via unsigned module load (lab)
Expected signal: Kernel ring buffer module-load message and updated /proc/modules; possible taint flag change.
- Test 3Auditd euid escalation event generation
Expected signal: auditd EXECVE/SYSCALL records tagged cve202653362 showing euid=0 with a non-root auid.
Response Playbook
Triage
- Identify the affected host's exact running kernel version (`uname -r`) and compare against the fixed stable releases containing the six patch commits; a host running an unpatched kernel plus escalation telemetry is high priority.
- Reconstruct the process ancestry of the root-owned child: capture the initiating non-root account, the interpreter used, and the full command lines to determine whether the elevation was legitimate (sudo/su) or anomalous.
- Check `dmesg`/journalctl for kernel oops, BUG, WARN, or taint messages timestamped near the escalation event, which often accompany memory-corruption kernel exploits.
- Correlate the triggering user account with recent authentication events and determine whether the account is expected to have any interactive root access.
Containment
- Isolate the affected host from the network (EDR network containment or switchport ACL) to prevent lateral movement while preserving volatile state.
- Suspend or disable the compromised user account and revoke active sessions and SSH keys associated with it.
- Prevent loading of untrusted kernel modules on comparable hosts (e.g. set `modules_disabled`, enforce module signing) until patching completes.
Evidence Collection
- Capture volatile memory and the full process list (LiME/AVML memory image plus `ps`, `/proc/<pid>` maps) before rebooting, since kernel exploits leave transient artifacts.
- Preserve auditd logs, `dmesg` ring buffer, journald, and `/var/log/` for the incident window along with the running kernel image and loaded module list (`lsmod`, `/proc/modules`).
Escalation Criteria
- ! Escalate to IR lead if kernel oops/taint messages coincide with confirmed non-root-to-root escalation on an unpatched kernel.
- ! Escalate if evidence shows loading of an unsigned/unknown kernel module or persistence mechanisms established after the escalation event.
- ! Escalate to the CISA KEV compliance owner given BOD 26-04 remediation timelines if the host cannot be patched within the mandated window.
Investigation Guide
Forensic Artifacts
- >
auditd SYSCALL/EXECVE records showing euid=0 with a non-root auid - >
Kernel ring buffer (dmesg) oops/BUG/taint entries - >
Loaded kernel module list (lsmod / /proc/modules) and module signing state - >
Process memory maps under /proc/<pid> for the escalated process
Tuning Guidance
Build an allowlist of legitimate privilege-escalation paths (sudo, su, pkexec, known setuid binaries, configuration-management agents, container runtimes) and their expected initiating accounts, then exclude those exe/comm values. Focus alerting on hosts whose kernel version predates the fixed stable releases. If auditd is not deployed, rely on EDR process-ancestry telemetry and add the interpreter-parent + root-child sequence as the primary signal.
Hunting Queries
Baselines non-root-to-root process transitions per host over a 7-day window to surface anomalous escalation clusters that deviate from expected sudo/su patterns.
DeviceProcessEvents | where Timestamp > ago(7d) | where InitiatingProcessAccountName != "root" and AccountName == "root" | summarize count() by DeviceName, InitiatingProcessAccountName, InitiatingProcessFileName, FileName | order by count_ desc index=linux (sourcetype=linux_audit OR sourcetype=auditd) euid=0 auid!=0 auid!=4294967295 | stats count values(comm) as comm values(exe) as exe by host, auid | sort - count Atomic Red Team Tests
In a lab, create a root-owned setuid helper and invoke it from an unprivileged shell to generate the non-root-to-root process telemetry this detection keys on (no real exploitation).
Command
cp /bin/bash /tmp/rootshell && sudo chown root:root /tmp/rootshell && sudo chmod 4755 /tmp/rootshell && sudo -u nobody /tmp/rootshell -p -c 'id' Cleanup
sudo rm -f /tmp/rootshell Expected Telemetry
Process launch of /tmp/rootshell with effective UID 0 initiated by user 'nobody'; auditd SYSCALL with euid=0 auid=nobody.
Expected Detection
Triggers the interpreter-parent to root-child correlation across all seven queries.
Load a benign out-of-tree unsigned kernel module to produce kernel taint and module-load telemetry associated with post-exploitation persistence.
Command
sudo modprobe dummy && dmesg | tail -n 5 && lsmod | grep dummy Cleanup
sudo rmmod dummy Expected Telemetry
Kernel ring buffer module-load message and updated /proc/modules; possible taint flag change.
Expected Detection
Supports forensicArtifacts collection and kernel-module hunting; flagged during evidence review.
Generate an auditd SYSCALL record where a non-root login UID reaches euid 0 through a shell, exercising the SPL/AQL/Sumo parsing logic.
Command
sudo auditctl -a always,exit -F arch=b64 -S execve -F euid=0 -k cve202653362 && su nobody -s /bin/bash -c 'sudo -n id' ; ausearch -k cve202653362 | tail -n 20 Cleanup
sudo auditctl -d always,exit -F arch=b64 -S execve -F euid=0 -k cve202653362 Expected Telemetry
auditd EXECVE/SYSCALL records tagged cve202653362 showing euid=0 with a non-root auid.
Expected Detection
Matches the auditd-based SPL, QRadar AQL, and Sumo Logic queries.