A security hole in Linux kernels prior to 2.6.32 was announced today.
It involves the mmap_min_addr system file found at
/proc/sys/vm/mmap_min_addr
Its default value is 0, which gives rise to the hole. You can set the value to something much larger, like 65536, and that will block the hole.
Here is how. Open a Konsole. Enter
sudo su
then, as root, issue
echo 65536 > /proc/sys/vm/mmap_min_addr
Close Konsole.
While this fixes the hole it also can cause problems with some VM services like WINE. Also, you'll have to repeat it with each boot up unless you add it to /etc/profile or some other script that runs during boot up.
I expect that a fixed kernel will be appearing in the repository before the bad guys have a chance to exploit it. If you don't do this fix then be sure that when you test your firewall at grc.com's "Shields Up!" web site that all 1024 port give you solid greens. That means that you are essentially invisible to hackers on the web trying to test your ports for weaknesses. If you don't respond they can only infer your presence from upstream server behaviors, and most aren't good enough to do that, or want to take the time.
Personally, I've got a great firewall so I am not going to worry about it.
It involves the mmap_min_addr system file found at
/proc/sys/vm/mmap_min_addr
Its default value is 0, which gives rise to the hole. You can set the value to something much larger, like 65536, and that will block the hole.
Here is how. Open a Konsole. Enter
sudo su
then, as root, issue
echo 65536 > /proc/sys/vm/mmap_min_addr
Close Konsole.
While this fixes the hole it also can cause problems with some VM services like WINE. Also, you'll have to repeat it with each boot up unless you add it to /etc/profile or some other script that runs during boot up.
I expect that a fixed kernel will be appearing in the repository before the bad guys have a chance to exploit it. If you don't do this fix then be sure that when you test your firewall at grc.com's "Shields Up!" web site that all 1024 port give you solid greens. That means that you are essentially invisible to hackers on the web trying to test your ports for weaknesses. If you don't respond they can only infer your presence from upstream server behaviors, and most aren't good enough to do that, or want to take the time.
Personally, I've got a great firewall so I am not going to worry about it.
Comment