What I want to know about kernel security updates

January 23, 2013

This is kind of a rant. The issue is on my mind because we spent a chunk of this evening applying kernel updates to our Ubuntu machines and rebooting them, something that we feel forced to do once every few months or so. One of the reasons that we don't do this more often, such as every time when Ubuntu releases a kernel update, is that kernel updates are among the most disruptive updates that there are; in order to make them take effect you must reboot the machine, which is completely disruptive to anyone using the machine (especially if they're logged in to it).

But another reason we don't apply Ubuntu kernel updates all that often is that Ubuntu's kernel updates are terrible at giving us useful information about how severe the issues are and how urgent doing an update is. Except in terribly obvious extreme situations (eg 'locally exploitable bug, gives root, an exploit is public') we wind up faced with a flurry of issues of extremely uncertain but generally low seeming impact. Unsurprisingly we wind up defaulting to not doing major disruptions on a regular basis, then periodically we decided that we should get up to date just in case.

While Ubuntu has its specific failings here, this is not just an Ubuntu problem. I think every Linux distribution I've seen a kernel security update from has failed to include the information we'd need to make meaningful decisions. All of them irritate me.

As a sysadmin, here is what I want to know about every issue fixed in a kernel security update:

  • how severe is the consequence of the issue? Does the exploit give you root, disclose some sort of information (and if so, what sort and can it be leveraged to disclose things like passwords), or just allow you to lock the machine up?

  • is this remotely exploitable or does it require running your code on the machine? If it's remotely exploitable, how remote is remote; 'on the same LAN' is a lot different than 'anyone on the Internet'.

    ('Exploitable from inside a VM' is another case.)

    The most common sort of issue that I see bugfixes for is a locally exploitable denial of service issue. While it's nice to fix these bugs, they are fundamentally unimportant for many sysadmins since any local user generally already has plenty of ways to lock up or crash a Unix system. But you'd never know this from how distributions phrase things in kernel update notices.

  • is this exploitable on a default configuration machine? Or does it require some specific hardware to be present or some specific, non-default configuration or protocol to have been set up?

    You would not believe how many updates don't make this clear. This matters hugely to whether a particular issue is even relevant to us and it makes me angry every time a distribution or vendor forces me to research this myself.

  • how currently exploitable is this issue? This ranges from 'a weaponized exploit has been made public' all the way through 'we think that someone might someday be able to figure out how to exploit this'.

    Yes, yes, I'm sure that distribution security teams hate having to say anything about this (unless it's the former), but trust me, this is the kind of thing that my manager asks me when I say 'this seems pretty urgent, I think we need to do an emergency reboot without our usual one-week advance notice (if there are no conference or paper deadlines)'.

  • what is the primary source for this issue, or at least what is an index page with links to the primary source information? Many kernel security issues are reported, disclosed, or announced on things like public mailing lists, generally with far more technical detail than the distribution wants to put in their update notice. I want to read this primary source material and I become angry when a distribution (which had all of this information itself) hides it and forces me to do web searches.

    And everyone should link to the CVE page for CVE issues as well. There is nothing I like quite so much as doing web searches for information that a distribution's security team already had but decided not to give me. Really.

I suspect that most distributions would want to put together their own information page in some standardized format. This is fine, just as long as they put a link to their own info page in the announcement and their info page links to the primary source (and the CVE information and so on). This would also be a good place to put extended discussions of things like how to tell if your particular system is potentially vulnerable to the issue.

My excessively cynical side suspects that distribution security teams leave out a lot of this information in order to push people towards applying every kernel update as soon as possible. If so, I have news for those security teams: they have it exactly backwards. There are powerful forces pushing us (and anyone) against applying updates, especially disruptive updates like new kernels. Every doubt and quibble and uncertainty in a kernel update message feeds those forces and makes it less likely that the update will be applied. In order to get us to apply an important update on an urgent basis, it must be clear that it is urgent. If it is not clear, everyone loses.

Everything works much better when the security team is honest and clear about kernel updates. We'll still sit on all of the updates that are just yet more ways for local users to lock the machine up, but that's no different than what we're already doing. But when you release something that's genuinely dangerous we'll be much more likely to notice, understand, and update much earlier than we would otherwise.

(By the way, for everyone who is about to advise us that we should have dynamic load balancers and pools of machines where we can take some out of service on a rolling basis for kernel upgrades and so on: there is no such thing as a general dynamic load balancer for user login sessions, established sessions in general, or actual running user processes. Thanks.)


Comments on this page:

From 115.70.177.211 at 2013-01-23 08:35:32:

Try ksplice: lwn.net/Articles/340477/

 ~Alex
By trs80 at 2013-01-23 09:04:49:

Yep, came here to say ksplice too.

From 76.10.173.95 at 2013-01-23 10:01:33:

I wonder if some of the reluctance to provide information is CYA-based. Eg, if for one vulnerability they freak out and tell you it's a remote root with hacks in the wild and then the next vulnerability they're not sure but it turns out to be just as bad. Then users will complain that they didn't properly warn about the second vulnerability, whereas in the current situation they can simply say "you should have done your research".

Obviously any accurate details they can easily provide you are welcome, but I can see them being afraid of the obligation to become a vulnerability management provider instead of just a software developer.

- Jeremy

By cks at 2013-01-23 12:17:33:

Unfortunately ksplice has three problems. First, it is not officially supported by Ubuntu. Second, ksplice is owned by Oracle. Third, it is only officially available from Oracle for Ubuntu's desktop version, not for the server version. The last may not make a difference in practice (although the ksplice management tool that Oracle's web pages show is a GUI), but it makes it more chancy to use ksplice on Ubuntu servers; if anything broke and we could even attract Oracle's attention, Oracle would probably just laugh at us. All of these combine together to make ksplice too risky for what is (for us) a minor gain.

In reply to Jeremy's comment: my view is that distribution security teams like Ubuntu's and RHEL's are already doing much of this assessment work. Ubuntu selectively backports fixes into their supported kernel versions, so the security team needs to analyze each new vulnerability to see if it applies to the Ubuntu kernel, assess if it's serious enough to backport, backport the fix, test the fix, and so on.

(This doesn't apply to a distribution like Fedora, which basically tracks the upstream kernel version closely. There the update team may well do no such assessment work and just periodically release the latest upstream with some necessary patches on top.)

From 66.175.95.4 at 2013-01-23 14:49:39:

The RedHat and CentOS update notices include a link to RedHat's Errata site, e.g. in this mornings announcement from CentOS (http://lists.centos.org/pipermail/centos-announce/2013-January/019208.html) about a new kernel update, it links to this site:

https://rhn.redhat.com/errata/RHSA-2013-0168.html

There RedHat explain in detail what is affected and why, and provide a link to the relevant CVEs. Its generally been more than enough detail to help me evaluate the need to patch / reboot.

From 71.202.160.69 at 2013-01-24 01:16:15:

I find RedHat's advisories to be very useful.

From 78.32.9.209 at 2013-01-25 17:35:06:

"My excessively cynical side suspects that distribution security teams leave out a lot of this information in order to push people towards applying every kernel update as soon as possible."

Security advisories typically include a summary of the impact so far as is known, though changelogs typically don't. For Debian kernel updates, the changelog generally includes the upstream summary and CVE number (if assigned) for each change; on occasion I've replaced an entirely useless summary with my own.

There are an awful lot of bugs for which the security impact is quite hard to determine. A use-after-free might result in a crash or it might result in privilege escalation, depending on many factors including build and system configuration. How much effort should distributors spend to work that out?

Debian also applies stable kernel updates from kernel.org, for which I try to summarise the impact in a bug report referenced by the changelog. For example: http://bugs.debian.org/698022

- Ben Hutchings


Written on 23 January 2013.
« Disaster recovery preparation is not the same as a DR plan
My Unix is a general purpose operating system »

These are my WanderingThoughts
(About the blog)

Full index of entries
Recent comments

This is part of CSpace, and is written by ChrisSiebenmann.
Twitter: @thatcks

* * *

Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web

This is a DWiki.
GettingAround
(Help)

Search:

Page tools: View Source, View Normal, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Wed Jan 23 02:03:34 2013
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.