First published: Thu Nov 04 2010(Updated: )
Description of problem: Structure sockaddr_tipc is copied to userland with padding bytes after "id" field in union field "name" unitialized. It leads to leaking of contents of kernel stack memory. We have to initialize them to zero. Reference: <a href="http://marc.info/?l=linux-netdev&m=128854507420917&w=2">http://marc.info/?l=linux-netdev&m=128854507420917&w=2</a> <a href="http://seclists.org/oss-sec/2010/q4/94">http://seclists.org/oss-sec/2010/q4/94</a> Acknowledgements: Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Linux |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-649717 is considered high due to potential leakage of kernel stack memory.
To fix REDHAT-BUG-649717, ensure that the padding bytes in the sockaddr_tipc structure are initialized to zero before copying to userland.
All versions of Red Hat Linux that include the vulnerable implementation of the sockaddr_tipc structure are affected by REDHAT-BUG-649717.
REDHAT-BUG-649717 is a memory leakage vulnerability caused by uninitialized padding bytes in a data structure.
A proper workaround for REDHAT-BUG-649717 involves updating the kernel to a version that includes the fix for the uninitialized padding issue.