The Update Conundrum
the.unknown-universe.co.uk
How a “kept back” Proxmox kernel left my home lab exposed to CVE‑2026‑31431 — why I now check upgradable packages and use apt full‑upgrade.

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.

  • ShortN0te@lemmy.ml
    1·
    8 hours ago

    I didn’t mean to put words in your mouth, but your replies are exhausting. Lighten up.

    I think you got my point. Not sure why you feel the need to try to discuss another discuasion topic with me.

    Apt could use some usability improvements, specifically around doing full upgrades. This isn’t a controversial take.

    No its not. And again, I never said apt is good or perfect or bad.

    Googling apt full upgrade CLI leads to various articles, all of which have a series of commands that are named orthogonally to this fairly common use case, and must be run in order, and sometimes repeated.

    I am fully aware, it is not like i ever had to dig down and resolve dependency hell.

    There’s good reasons it is the way it is, and it can certainly be improved.

    But it is something different if you say that tools could be made better, than writing a whole article with a click bait title on “How i ignored the output of my package manager”.