Linux kernel exit_thread allows elevated privileges
|linux-exitthread-gain-privileges (16106)||High Risk|
Linux kernel could allow a local attacker to gain elevated privileges on the system, caused by a vulnerability in the exit_thread function. The exit_thread function fails to invalidate the per-TSS io_bitmap pointer, which could result in certain processes inheriting IO access permissions. A local attacker could exploit this vulnerability to cause the system to crash or possibly gain root privileges on the system.
No remedy available as of August 1, 2014.
- Linux-Kernel Mailing List, Fri May 07 2004 - 10:11:51 EST : Bug in IO bitmap handling? Probably exploitable (2.6.5).
- Linux-Kernel Mailing List, Fri May 07 2004 - 11:40:06 EST: Re: Bug in IO bitmap handling? Probably exploitable (2.6.5).
- BID-10302: Linux Kernel Local IO Access Inheritance Vulnerability
- CVE-2004-2536: The exit_thread function (process.c) in Linux kernel 2.6 through 2.6.5 does not invalidate the per-TSS io_bitmap pointers if a process obtains IO access permissions from the ioperm function but does not drop those permissions when it exits, which allows other processes to access the per-TSS pointers, access restricted memory locations, and possibly gain privileges.
- OSVDB ID: 59969: Apache HTTP Server mod_ssl SSL / TLS Renegotiation Handshakes MiTM Plaintext Data Injection
- OSVDB ID: 5997: Linux Kernel IO Bitmap Access Permissions Inheritance
- SA11577: Linux Kernel IO Bitmap Access Permissions Inheritance Vulnerability
- Linux Kernel 2.6.0
- Linux Kernel 2.6.1 rc2
- Linux Kernel 2.6.1 rc1
- Linux Kernel 2.6.1
- Linux Kernel 2.6.3
- Linux Kernel 2.6.4
- Linux Kernel 2.6.5
- Linux Linux Kernel 2.6.2
May 07, 2004
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this