Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 630562 - kernel: additional stack guard patches [rhel-6.1]
kernel: additional stack guard patches [rhel-6.1]
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.1
All Linux
high Severity high
: rc
: ---
Assigned To: Johannes Weiner
Petr Beňas
: ZStream
Depends On:
Blocks: 630563 630564 666796
  Show dependency treegraph
 
Reported: 2010-09-06 04:28 EDT by Eugene Teo (Security Response)
Modified: 2015-01-04 17:59 EST (History)
14 users (show)

See Also:
Fixed In Version: kernel-2.6.32-92.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 630563 630564 (view as bug list)
Environment:
Last Closed: 2011-01-25 03:06:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0542 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update 2011-05-19 07:58:07 EDT

  None (edit)
Description Eugene Teo (Security Response) 2010-09-06 04:28:56 EDT
Description of problem:
Please backport:
  mm: make the mlock() stack guard page checks stricter
  7798330ac8114c731cfab83e634c6ecedaa233d7

  guard page for stacks that grow upwards
  8ca3eb08097f6839b2206e2242db4179aee3cfb3

  x86: don't send SIGBUS for kernel page faults
  96054569190bdec375fe824e48ca1f4e3b53dd36
Comment 2 Eugene Teo (Security Response) 2010-09-06 04:37:25 EDT
>   guard page for stacks that grow upwards
>   8ca3eb08097f6839b2206e2242db4179aee3cfb3

  testcase: http://lkml.org/lkml/2010/8/24/326
  https://patchwork.kernel.org/patch/127431/
Comment 5 Aristeu Rozanski 2010-12-16 15:54:14 EST
Patch(es) available on kernel-2.6.32-92.el6

Note You need to log in before you can comment on or make changes to this bug.