First published: Wed Sep 14 2005(Updated: )
The Linux kernel 2.6 before 2.6.12.1 allows local users to cause a denial of service (kernel panic) via a non group-leader thread executing a different program than was pending in itimer, which causes the signal to be delivered to the old group-leader task, which does not exist.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | =2.6.0 | |
Linux Kernel | =2.6.0-test1 | |
Linux Kernel | =2.6.0-test10 | |
Linux Kernel | =2.6.0-test11 | |
Linux Kernel | =2.6.0-test2 | |
Linux Kernel | =2.6.0-test3 | |
Linux Kernel | =2.6.0-test4 | |
Linux Kernel | =2.6.0-test5 | |
Linux Kernel | =2.6.0-test6 | |
Linux Kernel | =2.6.0-test7 | |
Linux Kernel | =2.6.0-test8 | |
Linux Kernel | =2.6.0-test9 | |
Linux Kernel | =2.6.1 | |
Linux Kernel | =2.6.1-rc1 | |
Linux Kernel | =2.6.1-rc2 | |
Linux Kernel | =2.6.2 | |
Linux Kernel | =2.6.3 | |
Linux Kernel | =2.6.4 | |
Linux Kernel | =2.6.5 | |
Linux Kernel | =2.6.6 | |
Linux Kernel | =2.6.6-rc1 | |
Linux Kernel | =2.6.7 | |
Linux Kernel | =2.6.7-rc1 | |
Linux Kernel | =2.6.8 | |
Linux Kernel | =2.6.8-rc1 | |
Linux Kernel | =2.6.8-rc2 | |
Linux Kernel | =2.6.8-rc3 | |
Linux Kernel | =2.6.9-2.6.20 | |
Linux Kernel | =2.6.10 | |
Linux Kernel | =2.6.10-rc2 | |
Linux Kernel | =2.6.11 | |
Linux Kernel | =2.6.11-rc2 | |
Linux Kernel | =2.6.11-rc3 | |
Linux Kernel | =2.6.11-rc4 | |
Linux Kernel | =2.6.11.5 | |
Linux Kernel | =2.6.11.6 | |
Linux Kernel | =2.6.11.7 | |
Linux Kernel | =2.6.11.8 | |
Linux Kernel | =2.6.11.11 | |
Linux Kernel | =2.6.12-rc1 | |
Linux Kernel | =2.6.12-rc4 | |
Linux Kernel | =2.6_test9_cvs |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-1913 is classified as a moderate severity vulnerability due to its potential to cause a denial of service.
To fix CVE-2005-1913, upgrade to Linux kernel version 2.6.12.1 or later.
CVE-2005-1913 affects local users of Linux kernel versions prior to 2.6.12.1.
The impact of CVE-2005-1913 is a kernel panic, leading to potential disruption of services.
CVE-2005-1913 is not a zero-day vulnerability as it has been publicly disclosed and can be mitigated through updates.