Advisory Published
Updated

REDHAT-BUG-642896

First published: Thu Oct 14 2010(Updated: )

Description of problem: The handling functions for sending and receiving messages, in rds_page_copy_user(), use the unchecked __copy_*_user_inatomic functions without any access checks on user-provided pointers. As a result, by passing a kernel address as an iovec base address in recvmsg-style calls, a local user can overwrite arbitrary kernel memory, which can easily be used to escalate privileges to root. Introduced via 7875e18e (v2.6.30-rc1). Acknowledgements: Red Hat would like to thank Dan Rosenberg of Virtual Security Research for reporting this issue.

Affected SoftwareAffected VersionHow to fix
Red Hat Linux>2.6.30-rc1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of REDHAT-BUG-642896?

    The severity of REDHAT-BUG-642896 is considered high due to the risk of exposing kernel memory and potential system compromise.

  • How do I fix REDHAT-BUG-642896?

    To fix REDHAT-BUG-642896, update the Linux Kernel to a version that addresses the improper handling of user-provided pointers.

  • What are the potential impacts of REDHAT-BUG-642896?

    The potential impacts of REDHAT-BUG-642896 include unauthorized access to sensitive kernel memory and potential exploitation by malicious users.

  • Which versions of Red Hat Linux are affected by REDHAT-BUG-642896?

    Red Hat Linux Kernel versions starting from 2.6.30-rc1 are affected by REDHAT-BUG-642896.

  • Is there a workaround for REDHAT-BUG-642896?

    Currently, there is no known workaround for REDHAT-BUG-642896 other than applying the appropriate kernel updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203