Debian LinuxOperating system · Debian
CVE-2025-22921
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 · uneditedFFmpeg git-master,N-113007-g8d24a28d06 was discovered to contain a segmentation violation via the component /libavcodec/jpeg2000dec.c.
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 · moderate confidenceA segmentation violation (SIGSEGV) exists in the FFmpeg JPEG2000 decoder (libavcodec/jpeg2000dec.c) that can be triggered by processing a specially crafted JPEG2000 file, causing the application to crash and resulting in denial of service.
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
Debian LinuxOperating system
= 11.0= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.1= 7.1.1= 7.1.2= 7.1.3= 7.2= 8.0= 8.0.1= 8.1CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FFmpeg is installedRun `ffmpeg -version` or `apt list --installed 2>/dev/null | grep -i ffmpeg`Affected if FFmpeg is not installed on the system, the system is not affected by this CVE.
-
Identify installed FFmpeg versionRun `ffmpeg -version` and note the version string (e.g., 7.1, 8.0.1)Affected if The installed version matches one of the affected versions: 7.0.x, 7.1.x, 7.2, 8.0, 8.0.1, or 8.1, indicating the decoder code contains the vulnerability.
-
Verify JPEG2000 decoder module existsRun `ffmpeg -decoders 2>/dev/null | grep -i j2k` or `ffmpeg -codecs 2>/dev/null | grep -i jpeg2000` to list available decodersAffected if A JPEG2000 decoder (j2k, jpeg2000) is listed as available, meaning the vulnerable code can be invoked when processing these files.
-
Check for active or recent JPEG2000 processingInspect any logs, scripts, or services that process media files; check for .jp2, .j2k, or .jpc file extensions in recent inputsAffected if FFmpeg is being used to process untrusted JPEG2000 files, as this is the attack vector that triggers the segmentation fault.
A system is affected if FFmpeg versions 7.0 through 8.1 are installed AND the JPEG2000 decoder is available AND the system processes or may process untrusted JPEG2000 media files.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedRestrict or disable processing of untrusted JPEG2000 media files in FFmpeg deployments until an official patch is released addressing the null pointer dereference or out-of-bounds access in the decoder.
FFmpeg 7.1 or later; Debian 11 security updates
- 1. Check the current FFmpeg version: ffmpeg -version
- 2. For Debian 11 systems, check for available security updates: apt update && apt list --upgradable
- 3. Apply system updates to receive the patched FFmpeg package: apt upgrade
- 4. If using static FFmpeg builds, download version 7.1 or later from ffmpeg.org/download.html
- 5. Verify the installed version after update: ffmpeg -version
- 6. Test that video processing functionality, particularly JPEG2000 decoding, works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22921 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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