dbcve.org
Linux KernelOperating system · Linux

CVE-2007-1730

MEDIUM · 6.6 CVSS v2.0 Published 2007-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 signedness error in the DCCP support in the do_dccp_getsockopt function in net/dccp/proto.c in Linux kernel 2.6.20 and later allows local users to read kernel memory or cause a denial of service (oops) via a negative optlen value.

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 signedness error in the DCCP protocol's getsockopt handler allows a local user to pass a negative optlen value, causing the kernel to perform out-of-bounds memory access. This can leak kernel memory contents or trigger a kernel oops (crash).

MitigationApply the relevant kernel patch to fix the signedness comparison in do_dccp_getsockopt(), then rebuild and deploy the patched kernel. Restrict local shell access as a defense-in-depth measure until patched.

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.20= 2.6.20.1= 2.6.20.2

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
None
Availability
Complete

AV:L/AC:L/Au:N/C:C/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' to get the running kernel version
    Affected if The version is 2.6.20, 2.6.20.1, or 2.6.20.2
  2. Verify DCCP protocol support is enabled
    Check the kernel configuration file (usually /boot/config-$(uname -r) or /proc/config.gz) for CONFIG_IP_DCCP, or run 'lsmod | grep dccp' to see if the dccp module is loaded
    Affected if DCCP is compiled into the kernel or the dccp module is loaded
  3. Check for active DCCP sockets
    Run 'cat /proc/net/dccp' or use 'ss -a' to list DCCP sockets if present
    Affected if Any DCCP sockets are in use or the /proc/net/dccp file exists with active entries
  4. Verify getsockopt system call availability
    Check that the kernel allows DCCP getsockopt calls by testing access or reviewing that DCCP protocol handling is active
    Affected if The system has DCCP enabled and allows socket option queries

You are affected if your kernel version is 2.6.20, 2.6.20.1, or 2.6.20.2 AND the DCCP protocol support is enabled or loaded.

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 relevant kernel patch to fix the signedness comparison in do_dccp_getsockopt(), then rebuild and deploy the patched kernel. Restrict local shell access as a defense-in-depth measure until patched.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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