lksctp Stream Control Transmission Protocol up to 2.6.16 deadlock

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in lksctp Stream Control Transmission Protocol up to 2.6.16. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in deadlock. This vulnerability is cataloged as CVE-2006-2275. There is no exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in lksctp Stream Control Transmission Protocol up to 2.6.16. It has been classified as problematic. This affects an unknown functionality. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. The summary by CVE is:

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 bug was discovered 05/06/2006. The weakness was shared 05/09/2006 as confirmed git commit (GIT Repository). The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2006-2275 since 05/09/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 22276 (CentOS 4 : kernel (CESA-2006:0575)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 115389 (Linux Kernel Unspecified Socket Buffer Handling Remote Denial of Service Vulnerability).

Upgrading to version 2.6.17 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published 4 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (26433), Tenable (22276), SecurityFocus (BID 17955†), OSVDB (26615†) and Secunia (SA20716†). The entries VDB-2071, VDB-2098, VDB-27880 and VDB-30335 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Deadlock
CWE: CWE-833 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22276
Nessus Name: CentOS 4 : kernel (CESA-2006:0575)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Stream Control Transmission Protocol 2.6.17
Patch: git.kernel.org

Timelineinfo

05/06/2006 🔍
05/06/2006 +0 days 🔍
05/09/2006 +3 days 🔍
05/09/2006 +0 days 🔍
05/09/2006 +0 days 🔍
05/12/2006 +3 days 🔍
06/19/2006 +38 days 🔍
08/22/2006 +64 days 🔍
08/23/2006 +1 days 🔍
08/30/2006 +7 days 🔍
03/12/2015 +3116 days 🔍
06/21/2025 +3754 days 🔍

Sourcesinfo

Advisory: git.kernel.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2006-2275 (🔍)
GCVE (CVE): GCVE-0-2006-2275
GCVE (VulDB): GCVE-100-30129

OVAL: 🔍

X-Force: 26433
SecurityFocus: 17955 - Linux Kernel 2.6.16.13 Multiple SCTP Remote Denial of Service Vulnerabilities
Secunia: 20716 - Ubuntu update for kernel, Moderately Critical
OSVDB: 26615 - CVE-2006-2275 - Lksctp - Denial-Of-Service Issue
Vulnerability Center: 12550 - Linux SCTP Denial of Service via Multiple Small Messages, Medium

See also: 🔍

Entryinfo

Created: 03/12/2015 12:19
Updated: 06/21/2025 22:17
Changes: 03/12/2015 12:19 (77), 06/24/2019 12:48 (4), 06/21/2025 22:17 (18)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!