REDHAT-BUG-684569
First published: Sun Mar 13 2011(Updated: )
While mm->start_stack was protected from cross-uid viewing (commit f83ce3e6b02d5e48b3a43b001390e2b58820389d), the start_code and end_code 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 start_code of "0" to mean a kernel thread and will misbehave. Thanks to Brad Spengler for pointing this out. <a href="https://lkml.org/lkml/2011/3/11/380">https://lkml.org/lkml/2011/3/11/380</a> Acknowledgements: Red Hat would like to thank Kees Cook for reporting this issue.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Linux |
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.
Reference Links
- https://lkml.org/lkml/2011/3/11/380
- https://access.redhat.com/support/policy/updates/errata/
- http://www.spinics.net/lists/mm-commits/msg82726.html
- http://git.kernel.org/linus/5883f57ca0008ffc93e09cbb9847a1928e50c6f3
- https://rhn.redhat.com/errata/RHSA-2011-0500.html
- https://rhn.redhat.com/errata/RHSA-2011-0498.html
- https://rhn.redhat.com/errata/RHSA-2011-0833.html
- https://bugzilla.redhat.com/show_bug.cgi?id=684569
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.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2011-0726
- agent/source
- agent/severity
- agent/description
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat linux