CVE-2005-3805
UnknownEPSS 0.40%
Last modified
CVE-2005-3805 is a vulnerability of currently unknown severity. A locking problem in POSIX timer cleanup handling on exit in Linux kernel 2.6.10 to 2.6.14, when running on SMP systems, allows local users to cause a denial of service (deadlock) involving process CPU timers.. EPSS estimates a 0.40% chance of exploitation in the next 30 days.
Description
A locking problem in POSIX timer cleanup handling on exit in Linux kernel 2.6.10 to 2.6.14, when running on SMP systems, allows local users to cause a denial of service (deadlock) involving process CPU timers.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | 2.6.10 |
| Linux | Linux Kernel | 2.6.11 |
| Linux | Linux Kernel | 2.6.11.1 |
| Linux | Linux Kernel | 2.6.11.2 |
| Linux | Linux Kernel | 2.6.11.3 |
| Linux | Linux Kernel | 2.6.11.4 |
| Linux | Linux Kernel | 2.6.11.5 |
| Linux | Linux Kernel | 2.6.11.6 |
| Linux | Linux Kernel | 2.6.11.7 |
| Linux | Linux Kernel | 2.6.11.8 |
| Linux | Linux Kernel | 2.6.11.9 |
| Linux | Linux Kernel | 2.6.11.10 |
| Linux | Linux Kernel | 2.6.11.11 |
| Linux | Linux Kernel | 2.6.11.12 |
| Linux | Linux Kernel | 2.6.12 |
| Linux | Linux Kernel | 2.6.12.1 |
| Linux | Linux Kernel | 2.6.12.2 |
| Linux | Linux Kernel | 2.6.12.3 |
| Linux | Linux Kernel | 2.6.12.4 |
| Linux | Linux Kernel | 2.6.13 |
| Linux | Linux Kernel | 2.6.14 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2005-3805?
A locking problem in POSIX timer cleanup handling on exit in Linux kernel 2.6.10 to 2.6.14, when running on SMP systems, allows local users to cause a denial of service (deadlock) involving process CPU timers.
How severe is CVE-2005-3805?
Severity scoring for CVE-2005-3805 is pending analysis. The EPSS model estimates a 0.40% probability of exploitation in the next 30 days.
How do I fix CVE-2005-3805?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2005-3805?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST