[SOLVED] New kernel in -current (32 bit, 64 bit) and in 14.1( 64 bit)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
patches/packages/linux-3.10.17-2/*:
These are new kernels that fix CVE-2014-0038, a bug that can allow local
users to gain a root shell.
Be sure to reinstall LILO (run "lilo" as root) after upgrading the kernel
packages, or on UEFI systems, copy the appropriate kernel to
/boot/efi/EFI/Slackware/vmlinuz).
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2014-0038
(* Security fix *)
Ok - so CVE-2014-0038 is really not too critical if you're running a laptop and you're really the only user and you also know the root login password :-)
Thing of course is that every time you install a new kernely, you have to re-install virtualbox and nvidia drivers (if you use them). And run lilo. And perhaps build a new initrd if you use that too. Thus a bit of a fag unless there's something motivating.
The danger is from a piggyback attack. Arbitrary code exploit in Firefox, flashplayer, java etc, or even things like xpdf, MPlayer, OpenOffice or any other app that references untrusted data, or god forbid a network facing server vulnerability, + CVE-2014-0038 = PWNED!
If you're running 64bit, do the update! It doesn't take much effort to re-run mkinitrd and /sbin/lilo.
Actually, for 14.1 users, I'd be inclined to borrow the .30 kernel from -current instead of the rebuilt .17 in patches/: lots of water under the bridge since .17 was released.
The danger is from a piggyback attack. Arbitrary code exploit in Firefox, flashplayer, java etc, or even things like xpdf, MPlayer, OpenOffice or any other app that references untrusted data, or god forbid a network facing server vulnerability, + CVE-2014-0038 = PWNED!
GazL reminds us that attackers can, and do, combine individual vulnerabilities to expand effective attack surfaces and/or amplify impact.
It's a mistake to believe you don't need to worry about CVE-2014-0038 in the single-user context.
Also, GazL's 3.10.30 recommendation highlights the wisdom in the way Pat structured the kernel deployment: 3.10.30 is available to interested 14.1 users (via current) but they can always fall back on 3.10.17 (patched for CVE-2014-0038) should they get bitten by
kernel regressions.
--mancha
Last edited by mancha; 02-20-2014 at 02:49 PM.
Reason: stylistic
I find it a little disconcerting that the kernel packages I have installed now (from the original 14.1 ISO) are build -3, but the security-fixed ones are build -2.
Greg Kroah-Hartman has announced the release of a new batch of stable kernels: 3.13.4, 3.12.12, 3.10.31, and 3.4.81.
heh! Typical. Always the day after.
Ivybridge owners might be interested in this one as the changelog mentions a fix for a "large performance regression", the rest mostly seems to be ARM related. I'll probably skip this one and wait for .32 (unless I get bored or anything important comes to light).
I'm a little surprised Greg hasn't EOL'd 3.12 yet with 4 releases of 3.13 out the door.
This only applies to x86_64 architecture only, not in x86
Yeah, I updated and posted too quickly without reading the changelog closely enough. Maybe ease up on the criticism a bit, okay? I think my post had some value.
@hitest: If it still allows you maybe it makes sense to edit the title so it also attracts the attention of 14.1 users
and not just current users. Maybe something like: "new kernels: 14.1 (64 bit) and current (32 & 64 bit)".
--mancha
PS Your post is fine, Pat upgraded kernels in 32 and 64 bit current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.