- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.
Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.
I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.
is this specific to apt? dnf or pacman dont suffer from this?
I don’t know about dnf, but pacman doesn’t do this by default. The only way to hold back packages is by writing it in the configuration.
I’ve not come across this with my non Debian based systems. Only use Debian for servers because it’s so stable, Arch and Fedora everywhere else!
I don’t know for certain but this seems pretty apt specific.