CVE-2010-0410: Medium severity Linux Linux kernel vulnerability
Description of problem: A problem was found in the drivers/connector/connector.c code where users could send/allocate arbitrary amounts of NETLINKCONNECTOR messages to the kernel, causing OOM condition, killing selected processes or halting the system.
This is fixed in mainline commit f98bfbd78c37c5946cc53089da32a5f741efdeb7 by removing the code.
commit f98bfbd78c37c5946cc53089da32a5f741efdeb7 Author: Evgeniy Polyakov <zbr> Date: Tue Feb 2 15:58:48 2010 -0800
connector: Delete buggy notification code.
On Tue, Feb 02, 2010 at 02:57:14PM -0800, Greg KH (gregkh) wrote: > > There are at least two ways to fix it: using a big cannon and a small > > one. The former way is to disable notification registration, since it is > > not used by anyone at all. Second way is to check whether calling > > process is root and its destination group is -1 (kind of priveledged > > one) before command is dispatched to workqueue. > > Well if no one is using it, removing it makes the most sense, right? > > No objection from me, care to make up a patch either way for this?
Getting it is not used, let's drop support for notifications about (un)registered events from connector. Another option was to check credentials on receiving, but we can always restore it without bugs if needed, but genetlink has a wider code base and none complained, that userspace can not get notification when some other clients were (un)registered.
Kudos for Sebastian Krahmer <krahmer>, who found a bug in the code.
Signed-off-by: Evgeniy Polyakov <zbr> Acked-by: Greg Kroah-Hartman <gregkh> Signed-off-by: David S. Miller <davem>
Acknowledgements:
Red Hat would like to thank Sebastian Krahmer for reporting this issue.
Other sources
drivers/connector/connector.c in the Linux kernel before 2.6.32.8 allows local users to cause a denial of service (memory consumption and system crash) by sending the kernel many NETLINKCONNECTOR messages.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2010-0410?
CVE-2010-0410 is considered a medium severity vulnerability due to its potential to cause out-of-memory (OOM) conditions.
How do I fix CVE-2010-0410?
To fix CVE-2010-0410, you should update your Linux kernel to version 2.6.32.9 or later.
Which software versions are affected by CVE-2010-0410?
CVE-2010-0410 affects several versions of the Linux kernel prior to 2.6.32.9, as well as specific Debian and Ubuntu releases.
What type of attack does CVE-2010-0410 allow?
CVE-2010-0410 allows attackers to send excessive NETLINK_CONNECTOR messages to the kernel, potentially leading to system instability.
Is CVE-2010-0410 present in modern kernels?
No, CVE-2010-0410 is not present in modern Linux kernels as it has been addressed in later versions.