Bug 88615 - known ptrace exploits are not killed after failed execution causing high load on the system
known ptrace exploits are not killed after failed execution causing high load...
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
: Security
Depends On:
  Show dependency treegraph
Reported: 2003-04-11 09:52 EDT by Vladimir Lazarenko
Modified: 2007-04-18 12:52 EDT (History)
2 users (show)

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

Attachments (Terms of Use)

  None (edit)
Description Vladimir Lazarenko 2003-04-11 09:52:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When you try to execute ptrace kernel exploit on the system, the exploit
procedure is terminated due to the fact that operation is not permitted. Alas,
the process itself still remains in the memory causing high load on the system.

exploit source can be found from http://www.lazarenko.net/ptrace.c

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. cc -o ptrace ptrace.c
2. ./ptrace
3. ps axuw | grep ptrace

Actual Results:  ptrace process, which supposed to be killed, remained in memory
slowly eating processor time, up to 100%.

Expected Results:  Process should have been killed completely, as it happens in
2.4.21-pre* kernel branch.

Additional info:
Comment 1 Vladimir Lazarenko 2003-04-11 11:22:04 EDT
I apologize, ptrace.c is available on that URL now.
Comment 2 Mark J. Cox 2003-05-30 05:34:09 EDT
This should be fixed by RHSA-2003:172
please reopen this bug if you still see this behaviour.

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