OSS-SEC: 432 Linux kernel CVEs (in less than 32 hours)

Discussion (6 Comments)Read Original on HackerNews

refp•about 3 hours ago

I remember when you were actually able to keep up with CVEs and you could (at least somewhat) prioritize patches while disregarding those which felt irrelevant.

But now.. are we simply supposed to use our f̶a̶v̶o̶r̶i̶t̶e̶ package manager and batch update our systems in a loop?

    while true; do apt-get update && apt-get upgrade -y; sleep 1d; done

wait. erhm... and probably an automatic reboot/kernel reload every 48h; THAT WILL DO IT! </sarcasm>

goodmythical•about 3 hours ago

Wire the script to a pressure sensor in your seat, save-all/update/reboot every time you get out of your chair.

Bonus points for relaunching programs open during initial execution of script.

refp•about 3 hours ago

perhaps we better add a job to automatically order new IoT devices from amazon too; once a month is probably good enough not to suffer. I think we just invented Upgrades-As-A-Service.. only $50/month for freshly not-yet-known-to-be-b0rked firmware!

are you gonna spot the LLM bill or should I?

meltyness•about 3 hours ago

... or that the kernel can't be hot reloaded is itself a vulnerability?

smallerize•about 3 hours ago

There are pro/enterprise features that can upgrade the linux kernel without downtime, like livepatch or kpatch. (The non-proprietary klp-build is still missing tooling for most distros I think.)

Avicebron•about 3 hours ago

Theoretically they should slow down. I suspect people will be much pickier about which apps to use in production. Which, ironically, will be directly at odds with more and more products being pumped out..

OSS-SEC: 432 Linux kernel CVEs (in less than 32 hours)

⚡ Community Insights

Discussion (6 Comments)Read Original on HackerNews