Bug 2346578 - CVE-2025-25473 ffmpeg: NULL Pointer Dereference in FFmpeg [epel-9]
Summary: CVE-2025-25473 ffmpeg: NULL Pointer Dereference in FFmpeg [epel-9]
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: ffmpeg
Version: epel9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Multimedia SIG
QA Contact:
URL:
Whiteboard: {"flaws": ["8eb68f82-8644-43a4-bc7b-8...
Depends On:
Blocks: CVE-2025-25473
TreeView+ depends on / blocked
 
Reported: 2025-02-19 11:53 UTC by Michal Findra
Modified: 2026-05-22 10:39 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-05-22 10:39:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Findra 2025-02-19 11:53:33 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2346414

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.

Comment 2 Fedora Admin user for bugzilla script actions 2025-06-15 15:45:19 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Dominik 'Rathann' Mierzejewski 2026-05-21 12:17:45 UTC
This is fixed in 7.1.2 and later.

Comment 4 Dominik 'Rathann' Mierzejewski 2026-05-22 10:39:07 UTC
Actually fixed in 8.0: https://github.com/FFmpeg/FFmpeg/commit/c08d300481b8ebb846cd43a473988fdbc6793d1b
and backported to 7.1.3: https://github.com/FFmpeg/FFmpeg/commit/baee5f5e2751b61572abe23a8f8a0042d27c89e6

Although, to me it's dubious that it made sense to backport the fix to older branches when the code calls ff_flush_packet_queue(s) a few lines later unconditionally (unlike in 8.0+).

Opened upstream issue: https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/23201

I'm going to close this because it looks like <8.0 is not affected.


Note You need to log in before you can comment on or make changes to this bug.