First published: Thu Dec 08 2011(Updated: )
Dereferencing a user pointer directly from kernel-space without going through the copy_from_user family of functions is a bad idea. Two of such usages can be found in the sendmsg code path called from sendmmsg, added by upstream commit c71d8ebe7a4496fb7231151cb70a6baa0cb56f9a. Usages are performed through memcmp() and memcpy() directly. Upstream fix: <a href="http://git.kernel.org/linus/bc909d9ddbf7778371e36a651d6e4194b1cc7d4c">http://git.kernel.org/linus/bc909d9ddbf7778371e36a651d6e4194b1cc7d4c</a> Acknowledgements: Red Hat would like to thank Tetsuo Handa for reporting this issue. Upstream acknowledges Mathieu Desnoyers as the original reporter.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Linux | =c71d8ebe7a4496fb7231151cb70a6baa0cb56f9a |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-761646 is classified as a high severity vulnerability due to potential memory corruption risks.
To fix REDHAT-BUG-761646, upgrade to an appropriate patched version of the Red Hat Linux Kernel that addresses this vulnerability.
Ignoring REDHAT-BUG-761646 may lead to system instability and increased risks of exploitation through memory corruption.
Only the version specified in the vulnerability, c71d8ebe7a4496fb7231151cb70a6baa0cb56f9a, is affected by REDHAT-BUG-761646.
Yes, REDHAT-BUG-761646 involves dereferencing user pointers in kernel space directly, highlighting risks with user input handling.