Bug 159919 - CAN-2005-1765 x86_64 crash (syscal-page-fix)
CAN-2005-1765 x86_64 crash (syscal-page-fix)
Status: CLOSED DEFERRED
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Peter Staubach
Brian Brock
source=vendorsec,public=20050602,impa...
: Security
Depends On:
Blocks: 145411
  Show dependency treegraph
 
Reported: 2005-06-09 05:39 EDT by Mark J. Cox (Product Security)
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-26 04:14:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Proposed patch (788 bytes, patch)
2005-06-09 05:39 EDT, Mark J. Cox (Product Security)
no flags Details | Diff

  None (edit)
Description Mark J. Cox (Product Security) 2005-06-09 05:39:05 EDT
Thus patch fixes a DoS affecting x86_64 2.6 where a compat mode program can hang
the kernel.
Comment 1 Mark J. Cox (Product Security) 2005-06-09 05:39:05 EDT
Created attachment 115255 [details]
Proposed patch
Comment 2 Mark J. Cox (Product Security) 2005-07-08 04:19:58 EDT
Looks public, fixed in a SUSE kernel
Comment 3 Peter Staubach 2005-07-15 16:15:07 EDT
I need some more information in order to facilitate integrating the changes
as suggested.

What problem is being described here?  The single sentence in the first
comment does not contain quite enough information.

How do I reproduce the problem?  I'd like to know whether the changes
really address the problem.
Comment 4 Mark J. Cox (Product Security) 2005-07-18 04:02:28 EDT
Sorry, we have no information other than that one line which was forwarded to us
on vendor-sec and the patch.  I've mailed the patch author and SUSE and cc'd
you, I hope this gives you the information you need.
Comment 5 Peter Staubach 2005-07-18 07:50:48 EDT
Hopefully, some of those folks will respond.  Otherwise, there is not really
sufficient information to 1) understand the changes and 2) test to see whether
they address a real problem or not.
Comment 6 Peter Staubach 2005-07-18 16:45:26 EDT
From the field:

> The patch is broken anyways, i would recommend to not apply it right now.

--

So, without some more information, it is not possible to proceed at this
time.  When some more information is available, then we can look at this
situation further.

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