OSV-2023-311
Heap-double-free in cache_bclose
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57939
Crash type: Heap-double-free
Crash state:
cache_bclose
bfd_close_all_done
fuzz_objdump.h
What each source reports
OSV No score
Heap-double-free in cache_bclose
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57939
Crash type: Heap-double-free
Crash state:
cache_bclose
bfd_close_all_done
fuzz_objdump.h
- Record
OSV-2023-311- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
binutilsOSS-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-2023-311 is a vulnerability with no CVSS score yet in binutils, published April 14, 2023. No source lists public exploit code. A source reports a fix.