Critical 'Copy Fail' Linux Kernel Vulnerability Exploited in the Wild: Privilege Escalation Risk
A nine-year-old local privilege escalation (LPE) vulnerability dubbed 'Copy Fail' (CVE-2026-31431) is actively being exploited in the wild, impacting numerous Linux distributions. The U.S. Cybersecurity and Infrastructure Security Agency (**CISA**) has added the flaw to its Known Exploited Vulnerabilities (KEV) catalog, urging immediate patching.

**CISA** has issued an alert regarding **CVE-2026-31431**, a local privilege escalation vulnerability affecting various Linux distributions. The vulnerability, also known as **Copy Fail**, allows an unprivileged local user to gain root access.
### Technical Details of Copy Fail
The vulnerability, tracked as **CVE-2026-31431** (CVSS score: 7.8), stems from an incorrect resource transfer within the Linux kernel. According to researchers at Theori and Xint, **Copy Fail** is a logic bug in the Linux kernel's authentication cryptographic template. This allows attackers to trivially trigger privilege escalation using a relatively small, 732-byte Python exploit. The flaw was introduced through seemingly innocuous changes to the Linux kernel in 2011, 2015, and 2017.
### Impact and Affected Systems
This high-severity vulnerability impacts Linux distributions shipped since 2017. It permits an unprivileged local user to obtain root-level access by corrupting the kernel's in-memory [page cache](https://en.wikipedia.org/wiki/Page_cache) of any readable file, including setuid binaries.
**Wiz**, a **Google**-owned security firm, explains that modifying the page cache effectively alters binaries at execution time without modifying the disk. This enables attackers to inject code into privileged binaries (e.g., /usr/bin/su) to gain root privileges.

### Containerized Environments at Risk
The prevalence of Linux in cloud environments significantly amplifies the impact of this vulnerability. **Kaspersky** warns that **Copy Fail** poses a serious risk to containerized environments like **Docker**, **LXC**, and **Kubernetes**. These platforms often grant processes inside a container access to the AF_ALG subsystem if the algif_aead module is loaded into the host kernel by default.
**Kaspersky** further notes that exploitation is relatively straightforward and difficult to detect, as the exploit utilizes only legitimate system calls. This makes it challenging to distinguish from normal application behavior.
### Exploit Availability and Threat Actor Activity
A fully functional proof-of-concept (PoC) exploit is publicly available. **Kaspersky** has detected Go and Rust versions of the original Python implementation in open-source repositories. The **Microsoft Defender Security Research Team** has observed preliminary testing activity, suggesting a potential increase in threat actor exploitation in the near future.
### Microsoft's Analysis and Attack Vectors
According to **Microsoft**, the attack vector is local and requires low privileges with no user interaction. While not remotely exploitable in isolation, it becomes highly impactful when chained with an initial access vector, such as Secure Shell (SSH) access, malicious CI job execution, or container footholds.
**Microsoft** outlined a potential attack scenario:
1. Reconnaissance to identify a vulnerable Linux host or container.
2. Preparation of a Python trigger.
3. Execution of the exploit from a low-privilege context.
4. Controlled 4-byte overwrite in the kernel page cache, leading to corruption of sensitive kernel-managed data.
5. Escalation to UID 0 and full root privileges.
### Remediation and Mitigation
Federal Civilian Executive Branch (FCEB) agencies are mandated to apply fixes by May 15, 2026. Patches have been released by affected Linux distributions. If immediate patching is not feasible, organizations should disable the affected feature, implement network isolation, and apply strict access controls.