FFmpeg up to 9.0.2 VVC decoder libavcodec/vvc/refs.c alloc_frame integer overflow

Summaryinfo

A vulnerability identified as problematic has been detected in FFmpeg up to 9.0.2. This impacts the function alloc_frame of the file libavcodec/vvc/refs.c of the component VVC decoder. Performing a manipulation results in integer overflow. This vulnerability is known as CVE-2026-125251. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability was found in FFmpeg up to 9.0.2. It has been classified as problematic. This affects the function alloc_frame of the file libavcodec/vvc/refs.c of the component VVC decoder. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

FFmpeg through 9.0.2 contains an integer overflow vulnerability in the VVC decoder alloc_frame() function in libavcodec/vvc/refs.c that undersizes the reference picture list allocation on 32-bit builds. Attackers can supply a crafted VVC (H.266) file with a very large number of NAL units per access unit to trigger heap out-of-bounds writes and corrupt memory.

The advisory is shared at code.ffmpeg.org. This vulnerability is uniquely identified as CVE-2026-125251 since 11/09/2026. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/09/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Multimedia Processing Software

Name

• FFmpeg

Version

• 9.0.0
• 9.0.1
• 9.0.2

License

• open-source

Website

• Product: https://ffmpeg.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion