dbcve.org
Linux KernelOperating system · Linux

CVE-2008-3276

HIGH · 7.1 CVSS v2.0 Published 2008-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Integer overflow in the dccp_setsockopt_change function in net/dccp/proto.c in the Datagram Congestion Control Protocol (DCCP) subsystem in the Linux kernel 2.6.17-rc1 through 2.6.26.2 allows remote attackers to cause a denial of service (panic) via a crafted integer value, related to Change L and Change R options without at least one byte in the dccpsf_val field.

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

Integer overflow in the DCCP protocol handler (dccp_setsockopt_change function) allows remote attackers to trigger a kernel panic via specially crafted Change L and Change R options that lack at least one byte in the dccpsf_val field. The vulnerability exists in Linux kernel versions 2.6.17-rc1 through 2.6.26.2.

MitigationUpgrade the Linux kernel to a version beyond 2.6.26.2 that includes the fix for this integer overflow, or apply the relevant upstream kernel patch. Consider disabling DCCP support in the kernel if not required.

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.17= 2.6.17.1= 2.6.17.2= 2.6.17.3= 2.6.17.4= 2.6.17.5= 2.6.17.6= 2.6.17.7= 2.6.17.8= 2.6.17.9= 2.6.17.10= 2.6.17.11

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:N/C:N/I:N/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 kernel version
    Run `uname -r` or read `/proc/version` to obtain the running kernel version
    Affected if The kernel version falls within 2.6.17 through 2.6.26.2 (inclusive)
  2. Determine if DCCP protocol support is loaded
    Run `lsmod | grep dccp` to list any loaded DCCP modules, or check `/proc/net/dccp` to see if the DCCP protocol is registered
    Affected if The dccp module is loaded or /proc/net/dccp exists and shows active connections
  3. Verify DCCP kernel configuration
    Check the kernel configuration file (often in /boot/config-`uname -r` or /proc/config.gz) for CONFIG_IP_DCCP=y or CONFIG_IP_DCCP=m
    Affected if DCCP support is compiled into the kernel (y) or as a loadable module (m)
  4. Check for active DCCP sockets
    Run `ss -x` or `netstat -x` and look for entries showing dccp protocol usage, or inspect /proc/net/dccp* for connection states
    Affected if There are any active DCCP sockets or connections listed

You are affected if your kernel version is between 2.6.17 and 2.6.26.2 AND the DCCP protocol is enabled or loaded in your environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Linux kernel to a version beyond 2.6.26.2 that includes the fix for this integer overflow, or apply the relevant upstream kernel patch. Consider disabling DCCP support in the kernel if not required.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-3276 — 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-2008-3276 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