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.

cross-posted from: https://lemmy.ml/post/46701277

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.

    • LeTak@feddit.orgEnglish
      0·
      17 days ago

      Just don’t use any command in proxmox. Proxmox is designed GUI first. It got an update button in the GUI. Only major releases could need tinkering in the terminal. But even changing repos is now possible in the GUI.

      • endlesseden@pyfedi.deep-rose.orgEnglish
        1·
        13 days ago

        gotta love that GUI, that bombards you with reminders to subscribe to their paid tier repository constantly and won’t let you update…

        also, provides no methodology to control when it wants to overwrite a config or when a externally added signable dkms exists and creates a prompt during dkms building.

        the gui is nice, but it’s far from perfect…

      • tofu@lemmy.nocturnal.gardenEnglish
        0·
        15 days ago

        I don’t know, I’ve seen it several times mentioned in the Proxmox forum. I think it’s more of a theoretical scenario but it’s strongly advised against.