Bug 149591 - CAN-2005-0178 tty/setsid race
CAN-2005-0178 tty/setsid race
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
impact=important,public=20050110
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-24 06:07 EST by Mark J. Cox (Product Security)
Modified: 2015-01-04 17:17 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-24 06:12:33 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)
Proposed patch from Debian (6.42 KB, patch)
2005-02-24 06:10 EST, Mark J. Cox (Product Security)
no flags Details | Diff

  None (edit)
Description Mark J. Cox (Product Security) 2005-02-24 06:07:14 EST
"Race condition in the setsid function in Linux before 2.6.8.1 allows
local users to cause a denial of service (crash) and possibly access
portions of kernel memory, related to TTY changes, locking, and
semaphores."

We originally believed this issue did not affect 2.4 kernels, however
this appears to be incorrect.
Comment 1 Mark J. Cox (Product Security) 2005-02-24 06:10:42 EST
Created attachment 111370 [details]
Proposed patch from Debian
Comment 2 Mark J. Cox (Product Security) 2005-02-24 06:12:33 EST
Actually, Alan said "In the 2.4 case your controlling tty is
private not thread group so a setsid() can't race because you can't
setsid in the same thread as is opening current->tty."

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