Re: Linux Update, patch tuesday.
Most all distributions do and just pass the updated kernel along in the next set of packages updated. Rolling releases have the simpler job, while release based distros generally have to backport the patches to whatever kernel version they use, but then it's they same passing along an updated package for the kernel as part of the normal update process.
Every distro, unless you build all packages from source, provides a package-manager for the purpose of installing, removing, and updating packages (among other chores). Whether that's RPM, deb, apt, pacman, zypper, etc... A lot of the distros go even farther and provide user convenience tools such as an update notification process, systray app, or the like, that provides notification when updates are available, and then it's simply a "click the icon" type install. Others prefer the command line and can use tools like pacman's 'checkupdates' to see what's pending, or simply start an update with zypper or apt and compare what is included in the proposed update.
The "scale" of the kernel CVE's may be up, (and many won't be show-stopper security issues), and I don't necessarily see that as a bad thing. I do share concern that in the interim it will overload those involved in the kernel patching process, but it's not as if the kernel is a new project or the people involved have shown signs they are not up for the job or able to manage patching and merging changes into the code base. I'm quite confident we are in good hands there.
Who is really hits hard are those organization that build a custom kernel for their use (for whatever reason or needed config options). Especially if they run on machines that are public facing. That's where the picking through the CVE list becomes the challenge and chore, and that's where the testing to ensure no side-effects impact their specific use case significantly adds to the work load. I don't envy those in that position, but for the normal Linux user, it's just a normal update that happens to include a new kernel and a reboot.
The really interesting part would be a summary from Greg KH of the items fixed and how they were identified/reported. Also whether the scale of the identified issues continues to increase or whether we go through a period where the bulk are identified and then it kind of trails off to a normal trickle. That's what I'll be watching.