REDHAT-BUG-684569: Low severity red hat linux vulnerability
While mm->startstack was protected from cross-uid viewing (commit f83ce3e6b02d5e48b3a43b001390e2b58820389d), the startcode and endcode values were not. This would allow the text location of a PIE binary to leak, defeating ASLR.
Note that the value "1" is used instead of "0" for a protected value since "ps", "killall", and likely other readers of /proc/pid/stat, take startcode of "0" to mean a kernel thread and will misbehave. Thanks to Brad Spengler for pointing this out.
https://lkml.org/lkml/2011/3/11/380
Acknowledgements:
Red Hat would like to thank Kees Cook for reporting this issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-684569?
The severity of REDHAT-BUG-684569 is considered to be critical due to the potential for ASLR (Address Space Layout Randomization) bypass.
How do I fix REDHAT-BUG-684569?
To fix REDHAT-BUG-684569, apply the latest security patches provided by Red Hat Linux that address this vulnerability.
What systems are affected by REDHAT-BUG-684569?
REDHAT-BUG-684569 affects versions of Red Hat Linux that utilize the affected mm->start_stack functionalities.
Could REDHAT-BUG-684569 lead to a complete system compromise?
Yes, REDHAT-BUG-684569 could potentially allow an attacker to gain unauthorized access and compromise the system by leaking memory addresses.
Is there a workaround for REDHAT-BUG-684569?
Currently, there are no known effective workarounds for REDHAT-BUG-684569 other than applying the appropriate patches.