Copy.Fail Linux Vulnerability
Overview
A newly disclosed Linux vulnerability, dubbed 'copy.fail', poses a serious risk across multiple distributions, including Ubuntu, RHEL, Debian, SUSE, Amazon Linux, and Fedora. Revealed by Theori on April 29, 2026, this local privilege escalation flaw allows attackers to manipulate the Linux kernel's crypto API to write unauthorized data into the page cache of files they do not own. Importantly, the exploit does not modify files on disk, making it difficult for traditional monitoring tools like AIDE and Tripwire to detect. This vulnerability is concerning because it affects a wide range of systems without requiring any specific modifications for different distributions. Organizations using these Linux variants should prioritize assessing their security posture and applying necessary mitigations to protect against potential exploitation.
Key Takeaways
- Affected Systems: Ubuntu, RHEL, Debian, SUSE, Amazon Linux, Fedora, and most other Linux distributions
- Action Required: Organizations should assess their security posture and apply necessary mitigations, including monitoring system behavior and potentially implementing kernel patches as they become available.
- Timeline: Disclosed on April 29, 2026
Original Article Summary
This is the worst Linux vulnerability in years. TL;DR copy.fail is a Linux kernel local privilege escalation, not a browser or clipboard attack. Disclosed by Theori on 29 April 2026 with a working PoC. It abuses the kernel crypto API (AF_ALG sockets) plus splice() to write four bytes at a time straight into the page cache of a file the attacker does not own. The exploit works unmodified across Ubuntu, RHEL, Debian, SUSE, Amazon Linux, Fedora and most others. No race condition, no per-distro offsets. The file on disk is never modified. AIDE, Tripwire and checksum-based monitoring see nothing. ...
Impact
Ubuntu, RHEL, Debian, SUSE, Amazon Linux, Fedora, and most other Linux distributions
Exploitation Status
The exploitation status is currently unknown. Monitor vendor advisories and security bulletins for updates.
Timeline
Disclosed on April 29, 2026
Remediation
Organizations should assess their security posture and apply necessary mitigations, including monitoring system behavior and potentially implementing kernel patches as they become available.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.
Related Topics: This incident relates to Linux, Exploit, Vulnerability, and 5 more.