CVE-2010-1488: Low severity Linux Linux kernel vulnerability
Description of problem: procoomscore(task) has a reference to taskstruct, but that is all. If this task was already released before we take tasklistlock - we can't use task->groupleader, it points to nowhere - it is not safe to call badness() even if this task is ->groupleader, hasintersectsmemsallowed() assumes it is safe to iterate over ->threadgroup list. - even worse, badness() can hit ->signal == NULL Add the pidalive() check to ensure unhashprocess() was not called. Also, use "task" instead of task->groupleader. badness() should return the same result for any sub-thread. Currently this is not true, but this should be changed anyway.
Upstream commit: http://git.kernel.org/linus/b95c35e76b29ba812e5dabdd91592e25ec640e93
Other sources
The procoomscore function in fs/proc/base.c in the Linux kernel before 2.6.34-rc4 uses inappropriate data structures during selection of a candidate for the OOM killer, which might allow local users to cause a denial of service via unspecified patterns of task creation.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2010-1488?
CVE-2010-1488 is classified as a high severity vulnerability due to its potential impact on the affected Linux Kernel versions.
How do I fix CVE-2010-1488?
To mitigate CVE-2010-1488, users should upgrade to a patched version of the Linux Kernel that addresses this vulnerability.
Which versions of the Linux Kernel are affected by CVE-2010-1488?
CVE-2010-1488 affects various versions of the Linux Kernel from 2.6.0 up to and including 2.6.34.
What are the potential impacts of CVE-2010-1488?
CVE-2010-1488 can lead to unpredictable behavior or exploitation of the system, which might compromise system security.
Is there a workaround for CVE-2010-1488?
There are no known effective workarounds for CVE-2010-1488 aside from upgrading to a safe version of the Linux Kernel.