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.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 6 months ago (5 children)

from my own experience, apt dist-upgrade removes old kernels, apt upgrade still installed the new kernel, grub updated and booted into the new kernel.

all dist-upgrade did (for me) was delete the old kernels. which is something I would prefer not to do because it removes any ability to rollback should I absolutely need to.

  • source
  • hideshow 5 child comments
  • [–] 2 points 6 months ago (4 children)

    Which distro? Debian for example always keeps two kernels: the curent one and the one in use before that, which is what I prefer, never had to rely on more than one backup kernel.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 6 months ago (3 children)

    Debian. like the Debian.

    currently running Trixie on my daily and bookworm on a couple servers which will be upgraded to Trixie soon.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 6 months ago (2 children)

    @GreenKnight23 @oong3Eepa1ae1tahJozoosuu I've never seen that behavior in Debian. Is that some different type of configuration?

  • source
  • parent
  • hideshow 2 child comments