OSV-2024-36
Heap-use-after-free in LLVMFuzzerRunDriver
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65647
Crash type: Heap-use-after-free READ 4
Crash state:
LLVMFuzzerRunDriver
absl::lts_NUMBER::random_internal::InitDiscreteDistribution
absl::lts_NUMBER::discrete_distribution<int>::param_type::init
What each source reports
OSV No score
Heap-use-after-free in LLVMFuzzerRunDriver
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65647
Crash type: Heap-use-after-free READ 4
Crash state:
LLVMFuzzerRunDriver
absl::lts_NUMBER::random_internal::InitDiscreteDistribution
absl::lts_NUMBER::discrete_distribution<int>::param_type::init
- Record
OSV-2024-36- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libavifOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2024-36 is a vulnerability with no CVSS score yet in libavif, published January 24, 2024. No source lists public exploit code. A source reports a fix.