in the next 48-72 hours, i intend to release a version of fig os that patches the dirty cow vulnerability.
the guardian (on oct 21) says it was already patched in debian. you can check to see if your (32-bit) refracta kernel is vulnerable with this command:
uname -a | grep 8u2
if it gives you kernel info, youre good. if not, run uname -a and look for 3.16.36 (the above check only applies to people running the 3.16.0-4 kernel: if it says "+deb8u1" its vulnerable.)
basically, you can modify files even if they are on a partition mounted as read-only (/sys and /proc are immune becase they dont have copy-on-write: "cow" support) and non-root users can modify executables that only root is supposed to be able to write to.
this is what you want for i686 machines: https://packages.debian.org/stable/kern ... -4-686-pae
i would link to the deb but it probably has deps you want to install too. (i will take care of that for fig os, which only has a 32-bit version.)
this is what you want for amd64 machines: https://packages.debian.org/stable/kern ... .0-4-amd64
you may be able to upgrade the kernel from the jessie-security repo. however, i tried this and im not sure it downloaded the 8u2 version.
whether this is due to amprolla or something i did, i dont know.
youre not going to be affected by this unless the attacker can run code on your system already. however, it means that every user is basically root. its a race-condition, but its not too difficult to exploit.
i try to cater to people running live; since fixing this requires one of the following:
* an upgrade and reboot
* an upgrade and live kernel patching
* a fixed live image (a remaster with a newer kernel version)
fig os 2.4 will feature the latter of those. the current version of fig os is 2.3: https://archive.org/download/Puppy_Linu ... gos2.3.iso https://archive.org/download/Puppy_Linu ... s23.fig.gz
i have little-to-no doubt that the next version of refracta will also fix this; hence the question in the title. its certainly more "urgent" for live users than installed users.
obviously if someone can run code on your system even as non-root, you have serious problems already-- but this makes it even worse.
info: https://security-tracker.debian.org/tra ... -2016-5195