The wait_for_unix_gc 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 SOCK_SEQPACKET sockets.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | * | 2.6.37 (excluding) |
| Linux_kernel | Linux | 2.6.37 (including) | 2.6.37 (including) |
| Linux_kernel | Linux | 2.6.37-rc1 (including) | 2.6.37-rc1 (including) |
| Linux_kernel | Linux | 2.6.37-rc2 (including) | 2.6.37-rc2 (including) |
| MRG for RHEL-5 | RedHat | kernel-rt-0:2.6.33.7-rt29.55.el5rt | * |
| Red Hat Enterprise Linux 4 | RedHat | kernel-0:2.6.9-89.35.1.EL | * |
| Red Hat Enterprise Linux 5 | RedHat | kernel-0:2.6.18-238.5.1.el5 | * |
| Red Hat Enterprise Linux 6 | RedHat | kernel-0:2.6.32-71.14.1.el6 | * |
| Linux | Ubuntu | hardy | * |
| Linux | Ubuntu | karmic | * |
| Linux | Ubuntu | lucid | * |
| Linux | Ubuntu | maverick | * |
| Linux | Ubuntu | natty | * |
| Linux | Ubuntu | upstream | * |
| Linux-ec2 | Ubuntu | karmic | * |
| Linux-ec2 | Ubuntu | lucid | * |
| Linux-ec2 | Ubuntu | maverick | * |
| Linux-ec2 | Ubuntu | upstream | * |
| Linux-fsl-imx51 | Ubuntu | karmic | * |
| Linux-fsl-imx51 | Ubuntu | lucid | * |
| Linux-fsl-imx51 | Ubuntu | upstream | * |
| Linux-lts-backport-maverick | Ubuntu | lucid | * |
| Linux-lts-backport-maverick | Ubuntu | upstream | * |
| Linux-lts-backport-natty | Ubuntu | upstream | * |
| Linux-mvl-dove | Ubuntu | karmic | * |
| Linux-mvl-dove | Ubuntu | lucid | * |
| Linux-mvl-dove | Ubuntu | maverick | * |
| Linux-mvl-dove | Ubuntu | upstream | * |
| Linux-source-2.6.15 | Ubuntu | dapper | * |
| Linux-source-2.6.15 | Ubuntu | upstream | * |
| Linux-ti-omap4 | Ubuntu | maverick | * |
| Linux-ti-omap4 | Ubuntu | upstream | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.