Remix.run Logo
▲ nightfly 2 hours ago

I've been doing Linux sys-admin work for 10+ years. Used to be I could read the full report on what ever vulnerabilities came out and triage which servers needed to be updated now and which could wait. A few years ago notifications started having so many it would take more time/effort to read everything than it would to patch everything. With this notification there's even ten times more...

▲Gigachad 22 minutes ago | parent | next [-]

That's because the methodology changed in 2024

>Note, due to the layer at which the Linux kernel is in a system, almost any bug might be exploitable to compromise the security of the kernel, but the possibility of exploitation is often not evident when the bug is fixed. Because of this, the CVE assignment team are overly cautious and assign CVE numbers to any bugfix that they identify. This explains the seemingly large number of CVEs that are issued by the Linux kernel team.

https://lwn.net/Articles/961961/

▲sippingabonedry an hour ago | parent | prev [-]

The amount of updates on Debian "stable" has become ridiculous, it's a daily rolling release of backports at this point.

Microsoft kinda got this right by doing it once a month, unless it's something horribly bad, you can plan your maintenance around a predictable calendar.

▲vortext an hour ago | parent [-]

You can choose to only install updates that require a restart once a month on Debian, then it's the same.