Comment by gwbas1c
11 days ago
> The kernels goes through an QA testing processes, and per this September post, they're looking at shortening the timeframe for kernel updates:
Looks like they aren't flexible enough to get a 4-line fix out the door when they need to.
These situations need a CEO or other high up to pull some people into a room, and basically say, "this needs to be released by EOD."
> Looks like they aren't flexible enough to get a 4-line fix out the door when they need to.
Perhaps because Ubuntu, like most distros, release new kernels that include fixes and updates for more than one issue:
* https://access.redhat.com/errata/RHSA-2026:93413
* https://launchpad.net/ubuntu/+source/linux/6.8.0-149.149
* https://www.suse.com/support/update/announcement/2026/suse-s...
* https://security-tracker.debian.org/tracker/DSA-6568-1
Perhaps that's the problem? Surely they use a version control system that allows them to branch off of older commit for these kinds of urgent patches.
So distros should release a new kernel for each CVE? Or only the "important" CVEs? And if two "important" ones come out two days apart there should be two kernels running through the QA pipeline? So that people can reboot their production systems two days apart?
7 replies →
This isn't a "bug in the queue," it's a severe security update that requires immediate patching.
Pretty much every software vendor has a way to ship fixes for 0-day exploits. They're called "hot fixes" and generally bypass normal releases. (IE, where I work, we can bypass our normal releases and publish emergency bugfixes in a matter of hours.)
That's why the fix needs a leader to basically pull everyone into a room and say "get it out by EOD."