Yesterday has been published an exploit which allows to make priviledge escalation from a non root user on every Linux installed since 2017. The exploit has been assigned number CVE-2026-31431, and nicknamed Copy Fail.
A fix is now available for Debian 12 and 13, onto which YunoHost 12 and (testing) 13 are based. We highly recommend to upgrade your system packages, for example, from the web admin ASAP. You should get an update for a linux-image-... package.
Raspberry Pi users, or probably users with hardware that requires a specific kernel build, check your provider’s usual software release channels for information about CVE-2026-31431.
After the upgrade you must reboot. If you don’t reboot, the old linux kernel could stay in use.
You should do it very quickly:
if you don’t trust your yunohost users (especially with apps that allow users to run their own shells or scripts, like JupyterLab)
apps which have regularly security problem giving access to a standard user like (e.g. some CMS like WordPress, unmaintained upstream).
if you have given some ssh permission to standard user or if you have set easy password on some account (and you miss to change it )
uname -v results to #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
and the contents of /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
# Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
#deb-src http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
#deb-src http://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
#deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Is the listing above in sources.list valid for all architectures? I am running on a Raspeberry Pi and it looks like this is managed by them and not directly by Debian right?
$ cat sources.list
deb http://raspbian.raspberrypi.org/raspbian/ bookworm main contrib non-free non-free-firmware rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bookworm main contrib non-free non-free-firmware rpi
and also
$ ls sources.list.d/
extra_php_version.list raspi.list yarn.list yunohost.list
$ cat sources.list.d/raspi.list
deb http://archive.raspberrypi.org/debian/ bookworm main
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.org/debian/ bookworm main
So I am wondering if this needs to be updated on the R-Pi foundation first …
No, from Debian repositories, or Raspbian’s if you have a Raspberry Pi. The fix for that CVE does not come from YunoHost but from the Linux kernel developers. (but now that I read again the first post, I can understand where that confusion comes from, I’ll rephrase it.)
I have those updates this morning for my Pi 5, do they patch the exploit ?:
linux-headers-rpi-2712 from 1:6.12.75-1+rpt1~bookworm to 1:6.12.87-1+rpt1~bookworm
linux-headers-rpi-v8 from 1:6.12.75-1+rpt1~bookworm to 1:6.12.87-1+rpt1~bookworm
linux-image-rpi-2712 from 1:6.12.75-1+rpt1~bookworm to 1:6.12.87-1+rpt1~bookworm
linux-image-rpi-v8 from 1:6.12.75-1+rpt1~bookworm to 1:6.12.87-1+rpt1~bookworm
libnghttp2-14 from 1.52.0-1+deb12u2 to 1.52.0-1+deb12u3
linux-libc-dev from 1:6.12.75-1+rpt1~bookworm to 1:6.12.87-1+rpt1~bookworm
raspi-firmware from 1:1.20250915-1~bookworm to 1:1.20260513-1~bookworm