CVE-2005-1768: Buffer Overflow

Published Jul 11, 2005
·
Updated

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.

Affected Software

92 affected components
Linux Linux kernel=2.4.18-pre1
Linux Linux kernel=2.4.15
Linux Linux kernel=2.4.30-rc3
Linux Linux kernel=2.4.0-test1
Linux Linux kernel=2.6.5
Linux Linux kernel=2.4.11
Linux Linux kernel=2.6.1
Linux Linux kernel=2.4.27-pre3
Linux Linux kernel=2.4.18-pre3
Linux Linux kernel=2.4.18-pre5
Linux Linux kernel=2.4.26
Linux Linux kernel=2.4.0-test6
Linux Linux kernel=2.4.19-pre1
Linux Linux kernel=2.4.21-pre7
Linux Linux kernel=2.6.10
Linux Linux kernel=2.4.27-pre2
Linux Linux kernel=2.4.12
Linux Linux kernel=2.4.13
Linux Linux kernel=2.6.0-test5
Linux Linux kernel=2.4.19-pre4
Linux Linux kernel=2.6.3
Linux Linux kernel=2.6.0-test2
Linux Linux kernel=2.4.17
Linux Linux kernel=2.6.4
Linux Linux kernel=2.6_test9_cvs
Linux Linux kernel=2.4.21-pre1
Linux Linux kernel=2.4.21
Linux Linux kernel=2.4.23_ow2
Linux Linux kernel=2.4.22-pre10
Linux Linux kernel=2.4.23
Linux Linux kernel=2.4.29-rc2
Linux Linux kernel=2.6.2
Linux Linux kernel=2.6.0-test11
Linux Linux kernel=2.4.0-test3
Linux Linux kernel=2.6.1-rc2
Linux Linux kernel=2.4.29-rc1
Linux Linux kernel=2.4.25
Linux Linux kernel=2.4.0-test8
Linux Linux kernel=2.4.24
Linux Linux kernel=2.6.0-test1
Linux Linux kernel=2.6.0-test6
Linux Linux kernel=2.4.23-pre9
Linux Linux kernel=2.4.31-pre1
Linux Linux kernel=2.4.30
Linux Linux kernel=2.4.28
Linux Linux kernel=2.4.0-test7
Linux Linux kernel=2.6.0-test4
Linux Linux kernel=2.6.0
Linux Linux kernel=2.4.24_ow1
Linux Linux kernel=2.4.18-pre4
Linux Linux kernel=2.4.19-pre6
Linux Linux kernel=2.4.10
Linux Linux kernel=2.4.0
Linux Linux kernel=2.4.2
Linux Linux kernel=2.4.30-rc2
Linux Linux kernel=2.4.19-pre2
Linux Linux kernel=2.4.0-test12
Linux Linux kernel=2.4.18-pre6
Linux Linux kernel=2.4.16
Linux Linux kernel=2.4.19-pre3
Linux Linux kernel=2.4.19
Linux Linux kernel=2.4.27-pre5
Linux Linux kernel=2.4.14
Linux Linux kernel=2.6.0-test10
Linux Linux kernel=2.4.27-pre1
Linux Linux kernel=2.4.0-test2
Linux Linux kernel=2.4.18
Linux Linux kernel=2.6.0-test9
Linux Linux kernel=2.4.19-pre5
Linux Linux kernel=2.4.21-pre4
Linux Linux kernel=2.4.22
Linux Linux kernel=2.4.0-test5
Linux Linux kernel=2.6.1-rc1
Linux Linux kernel=2.4.18
Linux Linux kernel=2.6.6-rc1
Linux Linux kernel=2.4.27-pre4
Linux Linux kernel=2.4.3
Linux Linux kernel=2.4.1
Linux Linux kernel=2.4.18-pre2
Linux Linux kernel=2.4.18-pre8
Linux Linux kernel=2.6.0-test7
Linux Linux kernel=2.4.27
Linux Linux kernel=2.4.0-test11
Linux Linux kernel=2.4.0-test4
Linux Linux kernel=2.4.0-test10
Linux Linux kernel=2.4.29
Linux Linux kernel=2.4.20
Linux Linux kernel=2.4.0-test9
Linux Linux kernel=2.6.0-test8
Linux Linux kernel=2.4.18-pre7
Linux Linux kernel=2.6.6
Linux Linux kernel=2.6.0-test3

Event History

Jul 11, 2005
CVE Published
04:00 AM
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-1768?

CVE-2005-1768 has a medium severity rating due to the potential for denial of service and execution of arbitrary code.

2

How do I fix CVE-2005-1768?

To fix CVE-2005-1768, update the Linux kernel to version 2.4.31 or later, or 2.6.6 or later.

3

Who is affected by CVE-2005-1768?

CVE-2005-1768 affects local users running Linux kernel versions 2.4 before 2.4.31 and 2.6 before 2.6.6.

4

What kind of attack does CVE-2005-1768 allow?

CVE-2005-1768 allows attackers to cause a kernel panic and possibly execute arbitrary code through a race condition.

5

Is there a workaround for CVE-2005-1768?

There is no stable workaround; the most effective mitigation is to upgrade the affected kernel versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203