CVE-2026-125270 · Runtime
NO FIX YET
FFmpeg through 9.0.2 reads past a heap buffer in v4l2_buffer_swframe_to_buf() when a frame has a negative linesize. An attacker who supplies a bottom-up AVI or PNM/PFM file can crash the application or leak heap memory into the encoded output.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems that run FFmpeg and transcode files from untrusted sources to a V4L2 M2M hardware encoder, typically embedded or Linux media boards. Deployments that only process trusted media or use software encoders are not shown to be exposed by these sources. unknown whether the sources list fixed versions.
Not affected if software-encoders-only, trusted-input-only
Who cares ffmpeg, linux, media-processing, v4l2
ffmpeg -version and compare it to the ranges in the NVD record.h264_v4l2m2m or hevc_v4l2m2m, in scripts or services that transcode untrusted files.No fix yet, per the sources.
FFmpeg through 9.0.2 contains a heap out-of-bounds read vulnerability in v4l2_buffer_swframe_to_buf() in libavcodec/v4l2_buffers.c that mishandles frames with negative linesize. Attackers can supply bottom-up AVI or PNM/PFM files that are transcoded to a V4L2 M2M encoder, crashing the application or leaking heap memory into encoded output.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.