Memory corruption via non-reentrant hardware-frame cleanup
Published Apr 17, 2024 · Updated Nov 4, 2025
Heap use-after-free in FFmpeg 6.1.1 allows remote attackers to corrupt memory when Vulkan hardware-frame initialization fails. The av_hwframe_ctx_init error path calls frames_uninit after vulkan_frames_init has already cleaned up, reentering non-reentrant cleanup and dereferencing freed heap state. Reachability requires an application to initialize Vulkan-backed hardware frames and encounter that failure path.
Summary
What happened
Heap use-after-free in FFmpeg 6.1.1 allows remote attackers to corrupt memory when Vulkan hardware-frame initialization fails. The av_hwframe_ctx_init error path calls frames_uninit after vulkan_frames_init has already cleaned up, reentering non-reentrant cleanup and dereferencing freed heap state. Reachability requires an application to initialize Vulkan-backed hardware frames and encounter that failure path.
The record
- CVE
- CVE-2024-31578
- Published
- Apr 17, 2024
- Updated
- Nov 4, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n6.1.1
What conditions does exploitation require?
What is affected?
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