OSV-2025-589
Heap-buffer-overflow in isvcd_decode_recon_tfr_nmb_base_lyr
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=435086517
Crash type: Heap-buffer-overflow READ 1
Crash state:
isvcd_decode_recon_tfr_nmb_base_lyr
isvcd_parse_inter_slice_data_cabac
isvcd_parse_pslice
What each source reports
OSV No score
Heap-buffer-overflow in isvcd_decode_recon_tfr_nmb_base_lyr
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=435086517
Crash type: Heap-buffer-overflow READ 1
Crash state:
isvcd_decode_recon_tfr_nmb_base_lyr
isvcd_parse_inter_slice_data_cabac
isvcd_parse_pslice
- Record
OSV-2025-589- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libavcOSS-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-2025-589 is a vulnerability with no CVSS score yet in libavc, published August 1, 2025. No source lists public exploit code. A source reports a fix.