CVE-2022-0847
Published: April 25, 2022
Official Description
Linux kernel contains an improper initialization vulnerability where an unprivileged local user could escalate their privileges on the system. This vulnerability has the moniker of "Dirty Pipe."
CISA KEV Advisory
Linux Kernel Privilege Escalation Vulnerability
Linux kernel contains an improper initialization vulnerability where an unprivileged local user could escalate their privileges on the system. This vulnerability has the moniker of "Dirty Pipe."
Apply updates per vendor instructions.
Risk Analysis
The Linux kernel contains an improper initialization vulnerability, dubbed "Dirty Pipe," which allows an unprivileged local user to escalate their privileges to root. With an EPSS score of 0.83439 and inclusion in CISA's KEV, this vulnerability is highly likely to be exploited for privilege escalation.
This vulnerability is actively being exploited in the wild, confirming its use by attackers. Exploitation requires local access to the system but can lead to full system compromise.
Linux system administrators should apply the latest kernel updates to patch the "Dirty Pipe" vulnerability. Regularly review and restrict user privileges to minimize the impact of local exploits.
Technical Analysis
CVE-2022-0847 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2022-0847 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2022-0847 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1