*** This bug has been split off bug 142802 ***
------- Original comment by Mark J. Cox (Security Response Team) on 2004.12.14
Reported on lkml a flaw that allows you to unlock someone
elses ipc memory (hence crossing permission boundary).
"In 2.6.8, the only processes that could lock shared memory segments
were those with CAP_IPC_LOCK. Unprivileged processes did not get a
Looks like this is 2.6.9 (Arjan says since the fixed rhel3 mlock stuff
got merged it might be there too)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.