Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. FFmpeg before commit 983dae9 contains an out-of-bounds read in the AV1 RTP packetizer (libavformat/rtpenc_av1.c). The keyframe detection loop that searches for a sequence header OBU advanced its pointer and remaining-size counter by the encoded header length plus the OBU payload size without first bounding the OBU size against the remaining data. A crafted OBU size causes the remaining-size counter to wrap to a positive value, causing the next loop iteration to dereference a pointer beyond the end of the packet buffer. A crafted AV1 input packet muxed to RTP triggers the out-of-bounds read.
Fixed in 9.0 and later (https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/f175bd50821f9adcded3acacc6b8e04037a92715) Not fixed in older branches.
Only F44 and older are affected.
Fixed in: 9.0.1: https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7646bb4c42e6837a9396c3d9ab8d8cf476e2053b (9.0 was affected, after all) 8.1.3: https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/1e565c3e9987536d661dd6bc5d102b61b69dbcbd F43 has 7.1, where the affected file does not exist.
FEDORA-2026-3e109a0c85 (ffmpeg-8.1.3-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-3e109a0c85
FEDORA-2026-3e109a0c85 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3e109a0c85` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3e109a0c85 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-3e109a0c85 (ffmpeg-8.1.3-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.