CVE-2025-10256: Ffmpeg: null pointer dereference in firequalizer filter (libavfilter/af_firequalizer.c)
A NULL pointer dereference vulnerability exists in FFmpeg’s Firequalizer filter (libavfilter/affirequalizer.c) due to a missing check on the return value of avmallocarray() in the configinput() function. An attacker could exploit this by tricking a victim into processing a crafted media file with the Firequalizer filter enabled, causing the application to dereference a NULL pointer and crash, leading to denial of service.
Other sources
A potential NULL pointer dereference vulnerability exists in FFmpeg's Firequalizer filter (libavfilter/affirequalizer.c) due to a missing check on the return value of avmallocarray() in the configinput() function. If the memory allocation for s->dumpbuf fails, the subsequent dereference of the returned pointer may cause a crash (denial of service).
The issue was introduced in commit d3be186ed1, which added the dumpfile and dumpscale options to the Firequalizer filter, but did not handle memory allocation failures for s->dumpbuf.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/ffmpegto a version that resolves this vulnerability.Fixed in 7:7.1.5-0+deb13u1Fixed in 7:9.0.2-4
Event History
Frequently Asked Questions
What is the severity of CVE-2025-10256?
CVE-2025-10256 is considered a high severity vulnerability due to the potential for a NULL pointer dereference that can lead to application crashes.
How do I fix CVE-2025-10256?
To fix CVE-2025-10256, update FFmpeg to the latest version where the NULL pointer dereference has been addressed.
What causes the vulnerability in CVE-2025-10256?
CVE-2025-10256 is caused by a missing check on the return value of av_malloc_array() in the config_input() function of FFmpeg's Firequalizer filter.
Who is affected by CVE-2025-10256?
Users of FFmpeg who utilize the Firequalizer filter in their media processing workflows may be affected by CVE-2025-10256.
Can CVE-2025-10256 be exploited remotely?
Yes, an attacker can exploit CVE-2025-10256 remotely by tricking a victim into processing a crafted media file that triggers the vulnerability.