dbcve.org
Linux KernelOperating system · Linux

CVE-2010-3080

HIGH · 7.2 CVSS v2.0 Published 2010-09-21
Fix available
A fix is available. Upgrade to 2.6.36 or later.
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
Double free vulnerability in the snd_seq_oss_open function in sound/core/seq/oss/seq_oss_init.c in the Linux kernel before 2.6.36-rc4 might allow local users to cause a denial of service or possibly have unspecified other impact via an unsuccessful attempt to open the /dev/sequencer device.

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

A double-free vulnerability exists in the snd_seq_oss_open function in sound/core/seq/oss/seq_oss_init.c of the Linux kernel before 2.6.36-rc4. When a local user makes an unsuccessful attempt to open the /dev/sequencer device, the function can trigger a double-free condition, potentially leading to denial of service or unspecified impact.

MitigationUpgrade the Linux kernel to version 2.6.36-rc4 or later, which contains the fix for this double-free vulnerability in the OSS sequencer initialization code.

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.36= 2.6.36
Ubuntu LinuxOperating system
Affected:= 6.06= 8.04= 9.04= 9.10= 10.04= 10.10
OpensuseOperating system
Affected:= 11.1
Linux Enterprise DesktopOperating system
Affected:= 11
Linux Enterprise Real Time ExtensionOperating system
Affected:= 11
Linux Enterprise ServerOperating system
Affected:= 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
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 the running kernel version
    Run 'uname -r' or 'cat /proc/version' to retrieve the kernel version. Compare the version number to the affected range: any version less than 2.6.36, or exactly 2.6.36, is affected.
    Affected if The kernel version is lower than 2.6.36 or is exactly 2.6.36.
  2. Verify the OSS sequencer module is available
    Check if the OSS sequencer is compiled into the kernel or loaded as a module by examining /boot/config-<version> (if available) for 'CONFIG_SND_SEQUENCER' set to 'y' or 'm', or run 'lsmod | grep seq_oss' to see if the module is loaded.
    Affected if The OSS sequencer (snd-seq-oss) is built into the kernel or loaded as a module, making the vulnerable code path reachable.
  3. Confirm the /dev/sequencer device exists
    Run 'ls -la /dev/sequencer' to check if the device file exists. If it does not exist, the vulnerability cannot be triggered.
    Affected if The /dev/sequencer device file exists and is accessible to local users.
  4. Check kernel configuration for OSS sequencer support
    If /boot/config-<version> is unavailable, check /proc/config.gz (if enabled) or look for the sequencer module in /lib/modules/$(uname -r)/kernel/sound/core/oss/ for the snd-seq-oss.ko module file.
    Affected if The snd-seq-oss module file is present in the kernel modules directory.

A system is affected if it runs a kernel version below 2.6.36 (or exactly 2.6.36) and has the OSS sequencer functionality enabled, which exposes the /dev/sequencer device that can trigger the double-free flaw.

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
Upgrade available Upgrade to 2.6.36 or later
Fixed in 2.6.36
Interim mitigation

Upgrade the Linux kernel to version 2.6.36-rc4 or later, which contains the fix for this double-free vulnerability in the OSS sequencer initialization code.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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