Chromium fuzzers have caught places where uninitialized data was used due
to calls to avio_read() not verifying that the number of bytes expected was
actually read. So updating the code to check the result from avio_read().

Attachment: 0001-Check-return-value-from-avio_read-to-verify-data-act.patch
Description: Binary data

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to