OSV-2023-68
Heap-buffer-overflow in isvcd_residual_samp_mb_dyadic
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56023
Crash type: Heap-buffer-overflow READ 2
Crash state:
isvcd_residual_samp_mb_dyadic
isvcd_process_residual_resample_mb
isvcd_process_inter_mb_rsd_pred_target_lyr
What each source reports
OSV No score
Heap-buffer-overflow in isvcd_residual_samp_mb_dyadic
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56023
Crash type: Heap-buffer-overflow READ 2
Crash state:
isvcd_residual_samp_mb_dyadic
isvcd_process_residual_resample_mb
isvcd_process_inter_mb_rsd_pred_target_lyr
- Record
OSV-2023-68- 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-2023-68 is a vulnerability with no CVSS score yet in libavc, published February 17, 2023. No source lists public exploit code. A source reports a fix.