CVE-2005-1768

Severity

37%

Complexity

19%

Confidentiality

106%

Race condition in the ia32 compatibility code for the execve system call in Linux kernel 2.4 before 2.4.31 and 2.6 before 2.6.6 allows local users to cause a denial of service (kernel panic) and possibly execute arbitrary code via a concurrent thread that increments a pointer count after the nargs function has counted the pointers, but before the count is copied from user space to kernel space, which leads to a buffer overflow.

Race condition in the ia32 compatibility code for the execve system call in Linux kernel 2.4 before 2.4.31 and 2.6 before 2.6.6 allows local users to cause a denial of service (kernel panic) and possibly execute arbitrary code via a concurrent thread that increments a pointer count after the nargs function has counted the pointers, but before the count is copied from user space to kernel space, which leads to a buffer overflow.

CVSS 2.0 Base Score 3.7. CVSS Attack Vector: local. CVSS Attack Complexity: high. CVSS Vector: (AV:L/AC:H/Au:N/C:P/I:P/A:P).

Overview

Type

Linux Kernel

First reported 19 years ago

2005-07-11 04:00:00

Last updated 7 years ago

2017-10-11 01:30:00

Affected Software

Linux Kernel 2.4.0

2.4.0

Linux Kernel 2.4.0 test1

2.4.0

Linux Kernel 2.4.0 test10

2.4.0

Linux Kernel 2.4.0 test11

2.4.0

Linux Kernel 2.4.0 test12

2.4.0

Linux Kernel 2.4.0 test2

2.4.0

Linux Kernel 2.4.0 test3

2.4.0

Linux Kernel 2.4.0 test4

2.4.0

Linux Kernel 2.4.0 test5

2.4.0

Linux Kernel 2.4.0 test6

2.4.0

Linux Kernel 2.4.0 test7

2.4.0

Linux Kernel 2.4.0 test8

2.4.0

Linux Kernel 2.4.0 test9

2.4.0

Linux Kernel 2.4.1

2.4.1

Linux Kernel 2.4.2

2.4.2

Linux Kernel 2.4.3

2.4.3

Linux Kernel 2.4.10

2.4.10

Linux Kernel 2.4.11

2.4.11

Linux Kernel 2.4.12

2.4.12

Linux Kernel 2.4.13

2.4.13

Linux Kernel 2.4.14

2.4.14

Linux Kernel 2.4.15

2.4.15

Linux Kernel 2.4.16

2.4.16

Linux Kernel 2.4.17

2.4.17

Linux Kernel 2.4.18

2.4.18

Linux Kernel 2.4.18 pre1

2.4.18

Linux Kernel 2.4.18 pre2

2.4.18

Linux Kernel 2.4.18 pre3

2.4.18

Linux Kernel 2.4.18 pre4

2.4.18

Linux Kernel 2.4.18 pre5

2.4.18

Linux Kernel 2.4.18 pre6

2.4.18

Linux Kernel 2.4.18 pre7

2.4.18

Linux Kernel 2.4.18 pre8

2.4.18

Linux Kernel 2.4.19

2.4.19

Linux Kernel 2.4.19 pre1

2.4.19

Linux Kernel 2.4.19 pre2

2.4.19

Linux Kernel 2.4.19 pre3

2.4.19

Linux Kernel 2.4.19 pre4

2.4.19

Linux Kernel 2.4.19 pre5

2.4.19

Linux Kernel 2.4.19 pre6

2.4.19

Linux Kernel 2.4.20

2.4.20

Linux Kernel 2.4.21

2.4.21

Linux Kernel 2.4.21 pre1

2.4.21

Linux Kernel 2.4.21 pre4

2.4.21

Linux Kernel 2.4.21 pre7

2.4.21

Linux Kernel 2.4.22

2.4.22

Linux Kernel 2.4.22 pre10

2.4.22

Linux Kernel 2.4.23

2.4.23

Linux Kernel 2.4.23 pre9

2.4.23

Linux Kernel 2.4.24

2.4.24

Linux Kernel 2.4.25

2.4.25

Linux Kernel 2.4.26

2.4.26

Linux Kernel 2.4.27

2.4.27

Linux Kernel 2.4.27 pre1

2.4.27

Linux Kernel 2.4.27 pre2

2.4.27

Linux Kernel 2.4.27 pre3

2.4.27

Linux Kernel 2.4.27 pre4

2.4.27

Linux Kernel 2.4.27 pre5

2.4.27

Linux Kernel 2.4.28

2.4.28

Linux Kernel 2.4.29

2.4.29

Linux Kernel 2.4.29 rc1

2.4.29

Linux Kernel 2.4.29 rc2

2.4.29

Linux Kernel 2.4.30

2.4.30

Linux Kernel 2.4.30 rc2

2.4.30

Linux Kernel 2.4.30 rc3

2.4.30

Linux Kernel 2.4.31 pre1

2.4.31

Linux Kernel 2.6.0

2.6.0

Linux Kernel 2.6 test1

2.6.0

Linux Kernel 2.6 test10

2.6.0

Linux Kernel 2.6 test11

2.6.0

Linux Kernel 2.6 test2

2.6.0

Linux Kernel 2.6 test3

2.6.0

Linux Kernel 2.6 test4

2.6.0

Linux Kernel 2.6 test5

2.6.0

Linux Kernel 2.6 test6

2.6.0

Linux Kernel 2.6 test7

2.6.0

Linux Kernel 2.6 test8

2.6.0

Linux Kernel 2.6 test9

2.6.0

Linux Kernel 2.6.1

2.6.1

Linux Kernel 2.6.1 Release Candidate 1

2.6.1

Linux Kernel 2.6.1 Release Candidate 2

2.6.1

Linux Kernel 2.6.2

2.6.2

Linux Kernel 2.6.3

2.6.3

Linux Kernel 2.6.4

2.6.4

Linux Kernel 2.6.5

2.6.5

Linux Kernel 2.6.6

2.6.6

Linux Kernel 2.6.6 Release Candidate 1

2.6.6

Linux Kernel 2.6.10

2.6.10

Stay updated

ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.

Get in touch

If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.