REDHAT-BUG-649717: Low severity red hat linux vulnerability
Description of problem: Structure sockaddrtipc 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: http://marc.info/?l=linux-netdev&m=128854507420917&w=2 http://seclists.org/oss-sec/2010/q4/94
Acknowledgements:
Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-649717?
The severity of REDHAT-BUG-649717 is considered high due to potential leakage of kernel stack memory.
How do I fix REDHAT-BUG-649717?
To fix REDHAT-BUG-649717, ensure that the padding bytes in the sockaddr_tipc structure are initialized to zero before copying to userland.
Which versions of Red Hat Linux are affected by REDHAT-BUG-649717?
All versions of Red Hat Linux that include the vulnerable implementation of the sockaddr_tipc structure are affected by REDHAT-BUG-649717.
What type of vulnerability is REDHAT-BUG-649717?
REDHAT-BUG-649717 is a memory leakage vulnerability caused by uninitialized padding bytes in a data structure.
Is there a workaround for REDHAT-BUG-649717?
A proper workaround for REDHAT-BUG-649717 involves updating the kernel to a version that includes the fix for the uninitialized padding issue.