If you installed Wine or Dosemu you're at risk

[Acid_1]

About the critical bug. blah blah blah.

If you installed Wine or Dosemu, open a terminal and type:

Code: Select all

cat /proc/sys/vm/mmap_min_addr

If it says 65536, you're safe. If it says 0, then you're vulnerable. To fix, do:

Code: Select all

sudo su
echo 65536 > /proc/sys/vm/mmap_min_addr

Then exit. You're safe and secure now. I didn't see anyone mention that, and I know lots of people here who migrated from Windows install Wine. Sorry if this is duplicate.

[Husse]

What did I miss?

[Acid_1]

You missed:

http://forums.linuxmint.com/viewtopic.php?f=6&t=31414

and

http://forums.linuxmint.com/viewtopic.php?f=61&t=31253

[Husse]

Holy cow - that makes three security alerts in a month with the ones I have reported in the newsletter
I have completely missed this one

[slider]

Good post Acid_1 !

Most of the Linux users that I know and myself included were not aware of this bug. I posted this info in our local LUG email list.

Two users of PCLOS so far were affected.

My Mint system was not affected, but this is something all users should check anyway just to be sure.

It was mentioned in our list that this fix may need to be run at boot each time for those affected. I havent researched this, but users who were affected may want to run the check command again after rebooting to see if things are still ok.

If things change back the affected user will need to place the patch in "/etc/rc.local" where it will be run each time at boot.

Thank you for posting this info.

[DrHu]

Yes mint 7 (Ubuntu 9.04..) should already be OK
https://bugs.launchpad.net/ubuntu/jaunt ... bug/413656

• WORK-AROUND:
  Ubuntu 8.04 and later have a default setting of 65536 in /proc/sys/vm/mmap_min_addr. When set, this issue is blocked. If your value is 0, please purge the "wine" and "dosemu" packages, and reset the value:

In terminal, check

• cat /proc/sys/vm/mmap_min_addr
  65536

[Acid_1]

Good post Acid_1 !

Most of the Linux users that I know and myself included were not aware of this bug. I posted this info in our local LUG email list.

Two users of PCLOS so far were affected.

My Mint system was not affected, but this is something all users should check anyway just to be sure.

It was mentioned in our list that this fix may need to be run at boot each time for those affected. I havent researched this, but users who were affected may want to run the check command again after rebooting to see if things are still ok.

If things change back the affected user will need to place the patch in "/etc/rc.local" where it will be run each time at boot.

Thank you for posting this info.

I just checked, and ya it goes back to zero on reboot so...

Code: Select all

gksu gedit /etc/rc.local

Then put in

echo 65536 > /proc/sys/vm/mmap_min_addr

Above the 'exit 0'

save it. Then in a terminal...

Code: Select all

sudo chmod +x /etc/rc.local

Now you're good on each reboot.

[SteveHoffmanUK]

Acid_!

Thanks very much for the heads-up on this. Both my Linux Mint 7 installations returned '0', so people shouldn't assume that they're OK if they have Mint 7. It reverted to '0' after reboot, so I used your reboot fix to make it permanent.

Well done.

[Husse]

I think rc.local already is executable

[Acid_1]

I think rc.local already is executable

You're probably right. When I was looking how to run scripts on boot, someone, somewhere on the vast internet said to make it executable. So I did lol. I didn't know

[metroid_maniac]

I had a value of 0, Fixed it now

EDIT: on Gloria that is