Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (deadlock) via a large number of small messages to a receiver application that cannot process the messages quickly enough, which leads to spillover of the receive buffer.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Stream_control_transmission_protocol | Lksctp | * | 2.6.17 (excluding) |
| Red Hat Enterprise Linux 4 | RedHat | kernel-0:2.6.9-42.EL | * |
| Linux-source-2.6.15 | Ubuntu | dapper | * |
| Linux-source-2.6.17 | Ubuntu | edgy | * |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.