CVE-2026-64832

FFmpeg 4.4 - 8.1.2 Double-Free in NVDEC Hardware Decoder via nvdec.c

Published Jul 22, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to trigger memory corruption by supplying a crafted video file. When no decoder surfaces remain, the ff_nvdec_start_frame_sep_ref error path frees memory via nvdec_fdd_priv_free while the calling layer subsequently frees the same frame description data, resulting in a double-free of the underlying decoder context in any FFmpeg-based application using NVDEC hardware-accelerated decoding.

Analysis

AI-generated

Technical impact

FFmpeg versions 4.4 through 8.1.2 contain a double‑free flaw in the NVIDIA NVDEC hardware decoder, identified as CWE-415. The bug manifests when the decoder's error path frees the frame description data twice, first through nvdec_fdd_priv_free and then by the calling layer. This double‑free corrupts the underlying decoder context memory and can allow an attacker to execute arbitrary code or crash the application that uses FFmpeg’s NVDEC accelerated decoding.

Affected Systems

Any installation of FFmpeg 4.4 up to and including 8.1.2 running on FFmpeg and invoking NVDEC decoding with user‑supplied video inputs are at risk.

Risk and Exploitability

The CVSS score of 8.7 indicates a high severity and potential to compromise confidentiality, integrity, and availability. The EPSS score is < 1%, indicating a very low but non‑zero probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, implying no publicly known exploit yet. The likely attack vector is local or remote delivery of a crafted video file that triggers the double‑free when a video stream is processed. Exploitation requires the attacker to supply the malicious file to a running FFmpeg instance that uses NVDEC accelerated decoding.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest FFmpeg release that fixes NVDEC double‑free (any post‑8.1.2 version).
  • Temporarily disable NVDEC hardware acceleration or reconfigure FFmpeg to use software decoding until a patch is installed.
  • Limit processing of untrusted video files by isolating FFmpeg in a sandboxed environment or defining an access control policy to restrict input sources.

Generated by OpenCVE AI on August 3, 2026 at 23:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8716-2 FFmpeg vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:ffmpeg:ffmpeg:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Ffmpeg
Ffmpeg ffmpeg
Vendors & Products Ffmpeg
Ffmpeg ffmpeg
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to trigger memory corruption by supplying a crafted video file. When no decoder surfaces remain, the ff_nvdec_start_frame_sep_ref error path frees memory via nvdec_fdd_priv_free while the calling layer subsequently frees the same frame description data, resulting in a double-free of the underlying decoder context in any FFmpeg-based application using NVDEC hardware-accelerated decoding.
Title FFmpeg 4.4 - 8.1.2 Double-Free in NVDEC Hardware Decoder via nvdec.c
Weaknesses CWE-415
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jul 28, 2026, 1:06 AM
Reserved
Jul 20, 2026, 6:27 PM
Status
Analyzed
Published
Jul 22, 2026, 6:17 PM
Modified
Oct 24, 2026, 3:10 PM