Memory leak via uncleared muxer packet queue
Published Feb 18, 2025 · Updated Dec 16, 2025
Memory leak in FFmpeg git master before commit c08d30 allows remote attackers to consume memory through a failed muxing process. The avformat_free_context cleanup path omits the FFFormatContext packet_buffer, leaving queued packets allocated when muxing fails. Reachability requires a muxing failure while packets remain queued; the public record identifies no specific triggering input or resulting service interruption.
Summary
What happened
Memory leak in FFmpeg git master before commit c08d30 allows remote attackers to consume memory through a failed muxing process. The avformat_free_context cleanup path omits the FFFormatContext packet_buffer, leaving queued packets allocated when muxing fails. Reachability requires a muxing failure while packets remain queued; the public record identifies no specific triggering input or resulting service interruption.
The record
- CVE
- CVE-2025-25473
- Published
- Feb 18, 2025
- Updated
- Dec 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo