REDHAT-BUG-561682
First published: Thu Feb 04 2010(Updated: )
Description of problem: A problem was found in the drivers/connector/connector.c code where users could send/allocate arbitrary amounts of NETLINK_CONNECTOR 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.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Linux | <f98bfbd78c37c5946cc53089da32a5f741efdeb7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://admin.fedoraproject.org/updates/kernel-2.6.31.12-174.2.17.fc12
- http://admin.fedoraproject.org/updates/kernel-2.6.30.10-105.2.23.fc11
- http://admin.fedoraproject.org/updates/kernel-2.6.31.12-174.2.19.fc12
- https://rhn.redhat.com/errata/RHSA-2010-0161.html
- https://rhn.redhat.com/errata/RHSA-2010-0398.html
- https://bugzilla.redhat.com/show_bug.cgi?id=561682
Frequently Asked Questions
What is the severity of REDHAT-BUG-561682?
The severity of REDHAT-BUG-561682 is high due to its potential to cause out-of-memory (OOM) conditions and system halts.
How do I fix REDHAT-BUG-561682?
To fix REDHAT-BUG-561682, update to the kernel version that includes the mainline commit f98bfbd78c37.
What systems are affected by REDHAT-BUG-561682?
REDHAT-BUG-561682 affects Red Hat Linux Kernel versions prior to commit f98bfbd78c37.
What are the potential consequences of exploiting REDHAT-BUG-561682?
Exploiting REDHAT-BUG-561682 could result in arbitrary message allocation leading to system crashes or termination of critical processes.
Is there a patch available for REDHAT-BUG-561682?
Yes, a patch addressing REDHAT-BUG-561682 is available with the kernel updates that include the fix in the specified commit.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2010-0410
- agent/severity
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat linux