Canonical Patches Two Kernel Vulnerabilities In Ubuntu 14.04 (softpedia.com) 33
jones_supa writes: Canonical has announced that a new kernel update is now live in the default software repositories for the Ubuntu 14.04 operating system. According to the security notice, two Linux kernel vulnerabilities have been fixed. The first security flaw was discovered in the SCTP (Stream Control Transmission Protocol) implementation, which conducted a wrong sequence of protocol-initialization steps. The second kernel vulnerability (discovered by Dmitry Vyukov) was in the Linux kernel's keyring handler, which tried to garbage collect incompletely instantiated keys. Both vulnerabilities allow a local attacker to crash the system by causing a denial of service. To fix the issues mentioned above, Canonical urges all users of Ubuntu 14.04 to update their kernel packages on all platforms.
Re: (Score:3)
Re: (Score:2)
I wouldn't be surprised to find more clients using it because it is a TCP/UDP mishmash that is good for multicasting, IPTV, and telco stuff. Of course, it will require new firewalls, since most will look at the packets, go, "is it TCP/UDP/IGMP/ICMP... if not, just drop them."
As for local attacks, I'm glad they are taken care of. Although not as show-stopping as a remote root bug, with containerization becoming mainstream, a bug that panics a kernel and drops a compute node can cause some headaches, even i
Re: (Score:2)
Is that safe?
Safer than not, in this case :-)
Re: Updating a kernel (Score:2)
I use the wily kernels with 14.04 and I haven't ran into any issues. Using patched kernels is probably safer than what I do.
Re: (Score:3)
Does anyone use SCTP? (Score:2)
It was supposed to be the successor to TCP with 1 -> N connection abilities IIRC, but to be blunt it seems to have died on its arse.
And how does that relate to the kernel? (Score:3)
Which versions have the vulnerabilities and where are they fixed? Did Ubuntu use an old, out-of-date kernel?
Re: (Score:1)
It's the Ubuntu kernel - which is also used by Linux.
Re: (Score:2)
Ah, no? Ubuntu may well maintain their own patch-set, as, for example, Red Hat is doing. And they may be way behind the official kernels.
Re: (Score:2)
So it is an Ubuntu problem, not a kernel problem.
Re: (Score:2)
Re: (Score:2)
Thanks and moron yourself. It is an Ubuntu problem.
Re: (Score:2)
No it isn't. It is a kernel problem for all Linux systems and distributions everywhere on the planet that use the versions of the kernel that have the vulnerabilities. Ubuntu is but one of thousands of unique Linux based OS systems, and this is simply stating that they have done so. People not on Ubuntu might also care, and the issue is certainly not specific to Ubuntu; only the fix is Ubuntu specific. Ubuntu has now patched their version of the Linux kernel. It is a kernel pr
Uh? Who will update? (Score:1)
But who will update? A kernel patch requires a reboot.
I think that those who still run 14.04 are running servers. And I hardly think a lot will update and reboot.
Re: (Score:2)
well, my desktop PC (also running 14.04) takes about 15 seconds off its SSDs, 6 of which spent by the BIOS. But it's not definitely a server.
And which hardware are you using? Mine takes 5+ minutes just for hardware initialization.
Thanks to Zarquon I am not running virtual fluff as the reboot would downtime all virtual machines.
I run an OCS [wikipedia.org] on my ones and a reboot is to be planned with a couple of months in advance with a test on a clone system.
A reboot is not a
Re:Uh? Who will update? (Score:4, Interesting)
I think that those who still run 14.04 are running servers. And I hardly think a lot will update and reboot.
That's an very strange assumtion. Of course server vulnerabilities are patched, and the machines rebooted if they need be. What did you expect? "Oh noes, my uptimes! I can't rebootz!"
My client is currently in the process of rolling out a new line of products based on Ubuntu 14.04 (the choice of distribution was not mine). Of course we'll be using patched kernels for new machines we build. Simply upgrading to whatever happens to be the latest version of Ubuntu this week is not an option. This has been a year in testing. The next major update is likely two to four years down the line. The previous one (which is still being shipped) is based on Ubuntu 8.04 (Hardy Heron).
Re: (Score:2)
I'm running 14.04 on my desktop PC. But since these vulnerabilities are both to local attackers and the worst they do is force a reboot, I'm not rushing to reboot.
Re: (Score:2)
I think that those who still run 14.04 are running servers.
14.04 is the most recent LTS release, so I would imagine that many desktop users are still running that version. Hell, 12.04 is still under support.
Why is this posted? (Score:2)
I've never been one to whine about stories being posted here, but this one has me particularly puzzled. Is there something novel about this particular set of patches? I ask because I've seen many, many kernel updates released by Canonical to my 14.04 boxes involving potential local exploits, since 14.04 was released. Anyone know why this one warrants a story, or is it just a slow news day?
Re: (Score:2)
I was wondering the same thing. My 14.04 laptop (my main work laptop) gets kernel updates from Canoncial not infrequently. Not sure why this one is special enough for /.