dbcve.org
Linux KernelOperating system · Linux

CVE-2008-2358

HIGH · 7.2 CVSS v2.0 Published 2008-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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_feat_change function in net/dccp/feat.c in the Datagram Congestion Control Protocol (DCCP) subsystem in the Linux kernel 2.6.18, and 2.6.17 through 2.6.20, allows local users to gain privileges via an invalid feature length, which leads to a heap-based buffer overflow.

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 subsystem's dccp_feat_change function allows local attackers to trigger a heap-based buffer overflow via invalid feature length values, enabling privilege escalation to root.

MitigationApply the upstream kernel patch for CVE-2008-2358 or upgrade to a kernel version beyond 2.6.20 that contains the fix; alternatively, disable DCCP via kernel configuration 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.18= 2.6.19= 2.6.20

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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 your kernel version
    Run 'uname -r' or 'cat /proc/version' to obtain the running kernel version
    Affected if The version matches 2.6.17, 2.6.18, 2.6.19, or 2.6.20 exactly
  2. Verify DCCP kernel module status
    Run 'lsmod | grep dccp' to see if the DCCP module is currently loaded
    Affected if The dccp module appears in the loaded module list
  3. Check if DCCP is built into the kernel
    Run 'cat /proc/config.gz' 2>/dev/null | gunzip | grep -i dccp, or check /boot/config-$(uname -r) for CONFIG_IP_DCCP=y
    Affected if CONFIG_IP_DCCP=y is set (DCCP compiled into the kernel)
  4. Verify DCCP module availability
    Run 'modinfo dccp' or check /lib/modules/$(uname -r)/net/dccp* files for existence
    Affected if The DCCP module files exist in the kernel modules directory

You are affected if your kernel version is 2.6.17 through 2.6.20 and the DCCP protocol is either loaded as a module or compiled into the kernel (the vulnerability requires DCCP to be available for exploitation).

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

Apply the upstream kernel patch for CVE-2008-2358 or upgrade to a kernel version beyond 2.6.20 that contains the fix; alternatively, disable DCCP via kernel configuration if not required.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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