Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 159921 - CAN-2005-1763 x86_64 crash (x86_64-ptrace-overflow)
CAN-2005-1763 x86_64 crash (x86_64-ptrace-overflow)
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Staubach
Brian Brock
: Security
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-06-09 05:47 EDT by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2005-514
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 09:24:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (765 bytes, patch)
2005-07-22 09:30 EDT, Peter Staubach
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:514 qe-ready SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 2 2005-10-05 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2005-06-09 05:47:31 EDT
There was a "off by one quad word" error in x86_64 ptrace. This was originally
thought to be unexploitable because it will only store into a unused area, but
better to plug it.  However Andi Kleen stated that it allows a write to a word
40 bytes into the page above the kernel stack of a process which may be exploitable.

Comment 1 Peter Staubach 2005-07-22 09:30:12 EDT
Created attachment 117054 [details]
Proposed patch
Comment 6 Red Hat Bugzilla 2005-10-05 09:24:45 EDT
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.