Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 159917 - CVE-2005-0756 x86_64 crash (ptrace-check-segment)
Summary: CVE-2005-0756 x86_64 crash (ptrace-check-segment)
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ernie Petrides
QA Contact: Brian Brock
Whiteboard: impact=important,source=vendorsec,pub...
Depends On:
Blocks: 156320
TreeView+ depends on / blocked
Reported: 2005-06-09 09:33 UTC by Mark J. Cox
Modified: 2007-11-30 22:07 UTC (History)
6 users (show)

Fixed In Version: RHSA-2005-663
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-09-28 15:18:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:663 0 qe-ready SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 6 2005-09-28 04:00:00 UTC

Description Mark J. Cox 2005-06-09 09:33:53 UTC
The following upstream patch fixes canonical checking for segment registers in
ptrace.  This allowed user programs to set a non canonical segment which would
cause oopses in the kernel later.

Comment 5 Ernie Petrides 2005-06-10 21:53:57 UTC
Reassigning this to myself.

Comment 6 Ernie Petrides 2005-06-11 01:43:58 UTC
Patch posted for review on 10-Jun-2005.

Comment 7 Mark J. Cox 2005-06-13 09:29:11 UTC
Actually CAN-2005-0756, fixing CVE name

Comment 9 Ernie Petrides 2005-06-15 01:06:07 UTC
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.8.EL).

Comment 15 Red Hat Bugzilla 2005-09-28 15:18:42 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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