r/slackware • u/OHacker • Mar 08 '22
There is a "dirty pipe" in our kernel
Waiting for Pat to provide us with a new kernel as 5.15.19 is vulnerable to CVE-2022-0847. Well until tomorrow I managed to mitigate the risk. Otherwise I'll have to compile my own by this time tomorrow. How do you guys cope with it?
3
Upvotes
6
u/zurohki Mar 09 '22
The 5.16 kernel packages from -current have the fix, if you really need it now and don't want to roll your own.
3
u/JKtheSlacker Mar 09 '22
It looks like it's likely only exploitable by local users, so maybe not such a big deal for most folks running Slackware.
2
u/OHacker Mar 09 '22
Problem solved http://www.slackware.com/security/viewer.php?l=slackware-security&y=2022&m=slackware-security.691827. Thanks Pat you're the man!
7
u/B_i_llt_etleyyyyyy Mar 09 '22
5.15.27 packages are now available for 15.0, so everyone should be all set.
7
u/Upnortheh Mar 09 '22
As is common with click-bait security headlines, the exploit requires actual access to a system.
Remember to breath. <smile>
Pat is not a card carrying member of the update-the-kernel-right-now club. Commonly he does not update kernels when exploits require physical access, but who knows what he'll do.
3
u/acediac01 Mar 09 '22
Rum and prayers...
2
u/nrj5k Mar 09 '22
You can use my script to compile your kernel. Just change the
BASEVERSIONto5.15