CVE-2010-4249: Medium severity Linux Linux kernel vulnerability

Published Nov 24, 2010
·
Updated

http://lkml.org/lkml/2010/11/23/395

Reported by Vegard Nossum: "I found this program lying around on my laptop. It kills my box (2.6.35) instantly by consuming a lot of memory (allocated by the kernel, so the process doesn't get killed by the OOM killer). As far as I can tell, the memory isn't being freed when the program exits either. Maybe it will eventually get cleaned up the UNIX socket garbage collector thing, but in that case it doesn't get called quickly enough to save my machine at least."

Reproducer: http://lkml.org/lkml/2010/11/23/395 Partial fix: http://lkml.org/lkml/2010/11/23/450 Remaining fix: http://marc.info/?l=linux-netdev&m=129059035929046&w=2

From Eric Dumazet: "we can eat all LOWMEM memory before unixgc() being called from unixreleasesock(). Moreover, the thread blocked in unixgc() can consume huge amount of time to perform cleanup because of huge working set.

One way to handle this is to have a sensible limit on unixtotinflight, tested from waitforunixgc() and to force a call to unixgc() if this limit is hit.

This solves the OOM and also reduce overall latencies, and should not slowdown normal workloads."

Acknowledgements:

Red Hat would like to thank Vegard Nossum for reporting this issue.

Other sources

The waitforunixgc function in net/unix/garbage.c in the Linux kernel before 2.6.37-rc3-next-20101125 does not properly select times for garbage collection of inflight sockets, which allows local users to cause a denial of service (system hang) via crafted use of the socketpair and sendmsg system calls for SOCKSEQPACKET sockets.

Launchpad

Affected Software

7 affected components
debian/linux-2.6
debian/user-mode-linux
Linux Linux kernel=2.6.37-rc2
Linux Linux kernel=2.6.37-rc1
Linux Linux kernel<2.6.37
Linux Linux kernel=2.6.37
Fedoraproject Fedora=13

Event History

Nov 24, 2010
Data Sourced
via Red Hat·02:55 AM
DescriptionSeverityAffected Software
Nov 29, 2010
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·09:52 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·10:42 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2010-4249?

CVE-2010-4249 is classified as a high severity vulnerability due to its potential to crash systems by consuming excessive memory.

2

Which Linux kernel versions are affected by CVE-2010-4249?

CVE-2010-4249 affects Linux kernel versions prior to 2.6.37, including the 2.6.35 version.

3

How do I fix CVE-2010-4249?

To resolve CVE-2010-4249, upgrade to at least Linux kernel version 2.6.37 or later.

4

What types of systems are vulnerable to CVE-2010-4249?

CVE-2010-4249 impacts systems running affected Linux kernel versions, including certain Debian and Fedora distributions.

5

What impact does CVE-2010-4249 have on a system?

CVE-2010-4249 can cause a denial of service by consuming a significant amount of memory, leading to system crashes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203