{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreialvzbcrxhu4qkz2phmcp2dwnqt6qliqbai7uce65gxiq5v66zzfe",
    "uri": "at://did:plc:q2k4ilmlzzrnoog5dccpqwor/app.bsky.feed.post/3mktqft3drpq2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidgc5adkfler3hxst3luzmsouljszqkyvovvvzm5wkrji24v3hc5i"
    },
    "mimeType": "image/webp",
    "size": 19360
  },
  "path": "/post/46701277",
  "publishedAt": "2026-05-01T16:29:13.000Z",
  "site": "https://lemmy.ml",
  "tags": [
    "Linux",
    "TheIPW",
    "27 comments",
    "https://the.unknown-universe.co.uk/tech-stories/update-conundrum/"
  ],
  "textContent": "submitted by TheIPW to linux\n72 points | 27 comments\nhttps://the.unknown-universe.co.uk/tech-stories/update-conundrum/\n\nI’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.\n\nTurns 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.\n\nI’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.",
  "title": "Turns out I have been updating wrong all this time! 🤦🏼"
}