Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2007-6720

mikmod: crash or abort when loading/playing multiple files with different number of channels

Overview

Published
20 Jan 2009
Modified
23 Apr 2026
Medium CVE
0 Registry packages
5 OS packages
3 Linux distributions
Yes Fix available

Description

libmikmod 3.1.9 through 3.2.0, as used by MikMod, SDL-mixer, and possibly other products, relies on the channel count of the last loaded song, rather than the currently playing song, for certain playback calculations, which allows user-assisted attackers to cause a denial of service (application crash) by loading multiple songs (aka MOD files) with different numbers of channels.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

debian 4 releases · 2 packages

fixed 8
sdl-mixer1-2 libmikmod
debian fixes for CVE-2007-6720
ReleasePackageFixed in
11 sdl-mixer1-2 1.2.8-1
11 libmikmod 3.1.11-6.1
12 sdl-mixer1-2 1.2.8-1
12 libmikmod 3.1.11-6.1
13 sdl-mixer1-2 1.2.8-1
13 libmikmod 3.1.11-6.1

2 more rows

echo 1 release · 2 packages

fixed 2
sdl-mixer1-2 libmikmod
echo fixes for CVE-2007-6720
ReleasePackageFixed in
sdl-mixer1-2 1.2.8-1
libmikmod 3.1.11-6.1

openSUSE 1 release · 1 package

fixed 1
libmikmod-devel
openSUSE fixes for CVE-2007-6720
ReleasePackageFixed inAdvisory
Tumbleweed libmikmod-devel +2 3.3.7-1.7 openSUSE-SU-2024:10305-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.