Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
18.104.22.168 (as of this date, 2008-02-08 15:25 patch-22.214.171.124.bz2 ) may not fully close this hole. The post before this is from Feb. 08. This is dated Feb. 10.
From: Bastian Blank <firstname.lastname@example.org>
Date: Sun, 10 Feb 2008 14:47:57 +0000 (+0200)
Subject: splice: fix user pointer access in get_iovec_page_array()
splice: fix user pointer access in get_iovec_page_array()
Commit 8811930dc74a503415b35c4a79d14fb0b408a361 ("splice: missing user pointer access verification") added the proper access_ok() calls to copy_from_user_mmap_sem() which ensures we can copy the struct iovecs from userspace to the kernel.
But we also must check whether we can access the actual memory region pointed to by the struct iovec to fix the access checks properly.
Signed-off-by: Bastian Blank <email@example.com>
Acked-by: Oliver Pinter <firstname.lastname@example.org>
Cc: Jens Axboe <email@example.com>
Cc: Andrew Morton <firstname.lastname@example.org>
Signed-off-by: Pekka Enberg <email@example.com>
Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
diff --git a/fs/splice.c b/fs/splice.c
index 14e2262..9b559ee 100644
@@ -1234,7 +1234,7 @@ static int get_iovec_page_array(const struct iovec __user *iov,
error = -EFAULT;
- if (unlikely(!base))
+ if (!access_ok(VERIFY_READ, base, len))
That's the info I found, if someone knows more/better, please post. See the discussion:
jayjwa, I've moved your post to a new thread. I think that with the amount of talk this vulnerability has generated on the blogosphere it merits an area for LQ members to discuss it if they wish. It's a pretty serious vulnerability, and AFAICT a huge number of distros had (or have) vulnerable kernels.
What is the short term measure one can employ before the patch is officially out?
The patches have been out for a couple days - 126.96.36.199 fixed CVE-2008-0009 and CVE-2008-0010, while 188.8.131.52 fixed CVE-2008-0600. I can also confirm that at least Debian, Ubuntu, and Slackware (the distros which I am familiar with) have released updated kernel packages with the fixes backported.
Last edited by win32sux; 02-15-2008 at 09:41 PM.
Reason: Specified kernel versions.
EDIT: Well, I think it's a pretty safe bet that you are, so I'm merging this.
The article from gentoo said it has been assigned to CVE-2008-0009 and CVE-2008-0010. I don't know what that means. The only thing I understood from that article is that kernels up to 2.6.23 were vulnerable.
The Gentoo site does provide a nice summary of the whole deal.
I'll quote it here for the benefit of anyone who might have been confused:
Two major security flaws in the Linux kernel were reported last weekend. Both flaws have the same impact (root access for local users) and both exist within the vmsplice() system call, which was added to the kernel in 2.6.17. There is no configuration option to exclude vmsplice() so everyone is vulnerable.
One of the security issues existed for the entire lifetime of vmsplice(), so any kernel version from 2.6.17 onwards is vulnerable. This was fixed in 184.108.40.206, 220.127.116.11 and 18.104.22.168. It has been assigned the vulnerability identifier of CVE-2008-0600.
The other security issue first appeared in 2.6.23. It was fixed in 22.214.171.124 and 126.96.36.199. This vulnerability has been assigned CVE-2008-0009 and CVE-2008-0010.
I've edited the thread title to make it a little clearer that this thread can be used to discuss any of those three CVEs.
Just to update on this, there is now malware appearing on various security forums using these issues.
Hope everyone is patched by now.
I'm confused...are you saying that there are documented attacks based on this exploit? Or are you saying that some security sites now have exploit code? If its the latter, from what I understand, there was exploit code out there approximately 2 weeks ago (proof-of-concept code)...people on some channels of freenode were using the exploit code to validate whether their patching was successful.
I'm confused...are you saying that there are documented attacks based on this exploit? Or are you saying that some security sites now have exploit code? If its the latter, from what I understand, there was exploit code out there approximately 2 weeks ago...people on some channels of freenode were using the exploit code to validate whether their patching was successful.
Yes, indeed. The initial impression I got from his post was that there was now some sort of attack based on this vulnerability carrying-out the actions he listed. But these actions could simply be part of one of the demo exploits which started floating-around a couple weeks ago (before the patches were released). Some clarification by jayjwa would be nice.