CVE-2005-0937: Low severity Linux Linux kernel vulnerability

Published Feb 22, 2005
·
Updated

Some futex functions in futex.c for Linux kernel 2.6.x perform getuser calls while holding the mmapsem semaphore, which could allow local users to cause a deadlock condition in dopagefault by triggering getuser faults while another thread is executing mmap or other functions.

Affected Software

107 affected components
Linux Linux kernel=2.6.11-rc3
Linux Linux kernel=2.5.29
Linux Linux kernel=2.6.11
Linux Linux kernel=2.5.54
Linux Linux kernel=2.5.68
Linux Linux kernel=2.5.3
Linux Linux kernel=2.5.20
Linux Linux kernel=2.5.12
Linux Linux kernel=2.6.5
Linux Linux kernel=2.5.40
Linux Linux kernel=2.5.21
Linux Linux kernel=2.6.1
Linux Linux kernel=2.5.0
Linux Linux kernel=2.5.13
Linux Linux kernel=2.5.47
Linux Linux kernel=2.5.35
Linux Linux kernel=2.5.62
Linux Linux kernel=2.5.51
Linux Linux kernel=2.5.14
Linux Linux kernel=2.5.67
Linux Linux kernel=2.6.10
Linux Linux kernel=2.5.24
Linux Linux kernel=2.5.64
Linux Linux kernel=2.5.27
Linux Linux kernel=2.6.11.6
Linux Linux kernel=2.5.17
Linux Linux kernel=2.6.0-test5
Linux Linux kernel=2.6.3
Linux Linux kernel=2.5.34
Linux Linux kernel=2.6.0-test2
Linux Linux kernel=2.5.65
Linux Linux kernel=2.6.4
Linux Linux kernel=2.6_test9_cvs
Linux Linux kernel=2.5.2
Linux Linux kernel=2.5.16
Linux Linux kernel=2.5.23
Linux Linux kernel=2.6.11.5
Linux Linux kernel=2.6.7-rc1
Linux Linux kernel=2.5.39
Linux Linux kernel=2.6.2
Linux Linux kernel=2.5.48
Linux Linux kernel=2.6.8-rc1
Linux Linux kernel=2.6.0-test11
Linux Linux kernel=2.5.30
Linux Linux kernel=2.6.1-rc2
Linux Linux kernel=2.6.11-rc4
Linux Linux kernel=2.5.60
Linux Linux kernel=2.5.32
Linux Linux kernel=2.6.8
Linux Linux kernel=2.6.0-test1
Linux Linux kernel=2.6.0-test6
Linux Linux kernel=2.5.45
Linux Linux kernel=2.5.22
Linux Linux kernel=2.5.25
Linux Linux kernel=2.5.1
Linux Linux kernel=2.5.19
Linux Linux kernel=2.6.10-rc2
Linux Linux kernel=2.6.0-test4
Linux Linux kernel=2.6.0
Linux Linux kernel=2.5.61
Linux Linux kernel=2.5.56
Linux Linux kernel=2.5.5
Linux Linux kernel=2.5.55
Linux Linux kernel=2.5.46
Linux Linux kernel=2.5.8
Linux Linux kernel=2.5.11
Linux Linux kernel=2.5.59
Linux Linux kernel=2.6.0-test10
Linux Linux kernel=2.5.42
Linux Linux kernel=2.5.41
Linux Linux kernel=2.5.33
Linux Linux kernel=2.6.0-test9
Linux Linux kernel=2.5.7
Linux Linux kernel=2.5.52
Linux Linux kernel=2.5.58
Linux Linux kernel=2.5.18
Linux Linux kernel=2.6.7
Linux Linux kernel=2.5.57
Linux Linux kernel=2.6.11-rc2
Linux Linux kernel=2.5.36
Linux Linux kernel=2.5.26
Linux Linux kernel=2.6.1-rc1
Linux Linux kernel=2.5.44
Linux Linux kernel=2.6.6-rc1
Linux Linux kernel=2.6.9-2.6.20
Linux Linux kernel=2.5.43
Linux Linux kernel=2.5.37
Linux Linux kernel=2.5.28
Linux Linux kernel=2.5.15
Linux Linux kernel=2.5.50
Linux Linux kernel=2.6.0-test7
Linux Linux kernel=2.5.66
Linux Linux kernel=2.5.38
Linux Linux kernel=2.5.10
Linux Linux kernel=2.5.9
Linux Linux kernel=2.5.63
Linux Linux kernel=2.5.4
Linux Linux kernel=2.6.8-rc2
Linux Linux kernel=2.5.31
Linux Linux kernel=2.6.8-rc3
Linux Linux kernel=2.5.53
Linux Linux kernel=2.5.49
Linux Linux kernel=2.5.6
Linux Linux kernel=2.6.0-test8
Linux Linux kernel=2.6.6
Linux Linux kernel=2.6.0-test3
Linux Linux kernel=2.5.69

Remediation

Event History

Feb 22, 2005
CVE Published
05:00 AM
Mar 30, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-0937?

CVE-2005-0937 has been classified with a high severity due to its potential to cause a deadlock in the Linux kernel.

2

How do I fix CVE-2005-0937?

To fix CVE-2005-0937, it is recommended to update to a patched version of the Linux kernel that addresses this vulnerability.

3

Which Linux kernel versions are affected by CVE-2005-0937?

CVE-2005-0937 affects multiple versions of the Linux kernel including 2.5.0 through 2.6.0.

4

Who is vulnerable to CVE-2005-0937?

Local users of affected Linux kernel versions are vulnerable to CVE-2005-0937, allowing them to cause potential system deadlocks.

5

What are the implications of CVE-2005-0937?

The implications of CVE-2005-0937 include disruption of services and potential denial of service due to deadlocks caused by the vulnerability.

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