Slashdot Mirror


Linux Kernel 2.6 Local Root Exploit

aquatix writes "This local root exploit (Debian, Ubuntu) seems to work everywhere I try it, as long as it's a Linux kernel version 2.6.17 to 2.6.24.1. If you don't trust your users (which you shouldn't), better compile a new kernel without vmsplice." Here is millw0rm's proof-of-concept code.

4 of 586 comments (clear)

  1. Re:Beauty of OSS by IBBoard · · Score: 4, Interesting

    And even if it isn't on its way (and while it isn't here) you can still get the source and remove the problematic part if you don't need it. Try recompiling Flash or some other commercial software without the section that has the exploit in ;)

    .

    Note: The above assumes that the kernel compiles, which may not always go as smoothly or be as you'd like. That doesn't change the fact that it is theoretically possible, though.

  2. Is this x86/x86_64 only? by the_humeister · · Score: 4, Interesting

    The proof-of-concept code only supports x86 and x86_64. Does that mean other architectures are immune?

  3. Re:Beauty of OSS by RonnyJ · · Score: 4, Interesting

    Looking at the comments at the top of the code, it's described as "quite old code" (assuming you believe the author).

  4. To everyone saying "I ca fix it myself"... by Toreo+asesino · · Score: 4, Interesting

    ...I have a question for you. I 100% agree this is an advantage of open-source than closed-source software will never have, ever. You've got me on that one, but my immediate thought was "ok, how much would I like to change my own kernel in production systems? About 0% thank-you-very-much".

    I mean, hacking stuff in and out of a production system kernel; surely that's a process that would require months of intensive regression testing, etc, etc? I mean, I doubt there are people that know the kernel well enough to do such changes for their own systems, but really, what percentage of you guys honestly and confidently can say "Yeah, let me just fix that for us" knowing your job is on the line if your systems crash around you.

    This isn't a troll, this is an honest question.

    --
    throw new NoSignatureException();