OSV-2021-622

Heap-buffer-overflow in frame_get_vlmetalayers

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33071

Crash type: Heap-buffer-overflow READ {*}
Crash state:
frame_get_vlmetalayers
frame_to_schunk
blosc2_schunk_from_buffer

What each source reports

OSV No score

Heap-buffer-overflow in frame_get_vlmetalayers

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33071

Crash type: Heap-buffer-overflow READ {*}
Crash state:
frame_get_vlmetalayers
frame_to_schunk
blosc2_schunk_from_buffer

Record: OSV-2021-622
Updated: 2026-11-02

Affected packages

Affected packages
Package	Affected	Fixed
`c-blosc2` OSS-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

History
Recorded	Changed	Sources
Nov 2, 2026	first indexed	OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2021-622 is a vulnerability with no CVSS score yet in c-blosc2, published April 10, 2021. No source lists public exploit code. A source reports a fix.

References

bugs.chromium.org/p/oss-fuzz/issues/detail?id=33071