105
submitted 17 hours ago by ekZepp@lemmy.world to c/linux@lemmy.world

Cybersecurity researchers have disclosed details of a Linux local privilege escalation (LPE) flaw that could allow an unprivileged local user to obtain root.

The high-severity vulnerability tracked as CVE-2026-31431 (CVSS score: 7.8) has been codenamed Copy Fail by Xint.io and Theori.

"An unprivileged local user can write four controlled bytes into the page cache of any readable file on a Linux system, and use that to gain root," the vulnerability research team at Xint.io and Theori said.

At its core, the vulnerability stems from a logic flaw in the Linux kernel's cryptographic subsystem, specifically within the algif_aead module. The issue was introduced in a source code commit made in August 2017.

Successful exploitation of the shortcoming could allow a simple 732-byte Python script to edit a setuid binary and obtain root on essentially all Linux distributions shipped since 2017, including Amazon Linux, RHEL, SUSE, and Ubuntu. The Python exploit involves four steps -

  • Open an AF_ALG socket and bind to authencesn(hmac(sha256),cbc(aes))
  • Construct the shellcode payload
  • Trigger the write operation to the kernel's cached copy of "/usr/bin/su"
  • Call execve("/usr/bin/su") to load the injected shellcode and run it as root

While the vulnerability is not remotely exploitable in isolation, a local unprivileged user can get root simply by corrupting the page cache of a setuid binary. The same primitive also has cross-container impacts as the page cache is shared across all processes on a system.

you are viewing a single comment's thread
view the rest of the comments
[-] A_norny_mousse@piefed.zip 22 points 16 hours ago

Most LTS distros have security updates enabled ootb.

[-] r00ty@kbin.life 7 points 16 hours ago

I mean I updated my servers and some of them on LTS releases that were not the very latest one were still vulnerable after a reboot. Hence I disabled the module on those servers. So it's worth checking your version definitely has a fix available.

[-] sem@piefed.blahaj.zone 5 points 13 hours ago
[-] Successful_Try543@feddit.org 3 points 8 hours ago* (last edited 6 hours ago)

~~It could be for example Debian 12 (Bookworm). While Debian 13 (Trixie) already got fixed, Bookworm is still vulnerable.~~

Edit: It just got fixed.

https://security-tracker.debian.org/tracker/CVE-2026-31431

[-] r00ty@kbin.life 3 points 1 hour ago

Yeah one of them was Debian 12 for sure.

this post was submitted on 01 May 2026
105 points (100.0% liked)

Linux

17336 readers
155 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS