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.
I'm not sure if the concept is the real thing, but there is a kernel patch for this exploit on git, I have seen it yesterday.
Just posted because the source web page noted all kernels > 3.8 were affected, I did not test the code that was made public by the author.
Seems that debian and some other distros were patched for it recently, and I've seen comments saying grsec prevents this from happening.
Thank you for testing this, much appreciated.
I'll be testing 32-bit and 14.1 as well. Earlier versions than 14.1 won't be vulnerable.
The exploit did not work here on -current or 14.1, 64-bit or 32-bit. Earlier versions lack the supposedly vulnerable code.
I have run the example in Slackware 14.1 64 bits with kernel 3.10.17 (serie) and 3.10.90 (compiled by me) and according to the example both kernels are malfunctioning.
I have run the example in Slackware 14.1 64 bits with kernel 3.10.17 (serie) and 3.10.90 (compiled by me) and according to the example both kernels are malfunctioning.
Yes, the leak.c example shows a problem here as well, but the exploit does not succeed in gaining elevated privileges. Have you tested that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.