Copy Fail
| CVE identifier | CVE-2026-31431 |
|---|---|
| CVSS score | 7.8 |
| Date of public disclosure | April 29, 2026 |
| Discoverer | Taeyang Lee (Theori) |
| Affected software | Linux kernel |
| Website | copy |
CVE-2026-31431, commonly known as Copy Fail, is a vulnerability in the Linux kernel that allows unauthorized privilege escalation,[1][2] disclosed by security firm Theori to the public on 29 April 2026 and to the Linux kernel security team five weeks prior.[3] The exploit blends into normal system activity via standard system calls and may be raised through 10 lines of Python.[4]
The vulnerability lets an unprivileged user make use of the address family AF_ALG in the Crypto API of the Linux kernel to perform controlled 4‑byte writes into the page cache, which backs the in‑memory copies of files.[5]
By replacing code in the in‑memory copy of a readable executable stored in the page cache, an attacker can escalate user privileges when any privileged process later runs that corrupted version of the file. As most Linux utilities for changing users (e.g. su) run as privileged using setuid, the user privilege escalation surface is large.
Every Linux distribution using Linux kernel versions between 4.14 (2017[2]) and 6.19.12 is at risk.[6][7] Debian, Ubuntu, SUSE, Red Hat Enterprise Linux, and other Linux distributions were affected.[2][8]
Many distributions and security sources recommended mitigating the issue via disabling the affected algif_aead kernel module.[6][8] Some distributions—such as Arch Linux, Fedora,[3] and Amazon Linux—had released patches at the time of the disclosure,[9] but the vulnerability was disclosed by Theori before the affected distributions they advertised as vulnerable had released patches.[3] As of 30 April 2026[update], SUSE, Red Hat, and Ubuntu have released mitigation guidance.[3] As of May 5, detection rules from Kaspersky Lab have been added.[4]
MAC mechanisms such as SELinux and AppArmor can mitigate the exploit, but only when they are configured so that only legitimately required services are granted access to the AF_ALG socket family. In default configurations, any unconfined or broadly permitted process can still open AF_ALG sockets, so the protection is effectively absent and the exploit remains reachable.[10]
According to GrapheneOS, Android is unaffected due to its use of SELinux policies, where only the dumpstate process (used for bug reports) is permitted to create AF_ALG sockets.[11]
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.