OSV-2020-941
Heap-buffer-overflow in gc_mark_string
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19780
Crash type: Heap-buffer-overflow READ 4
Crash state:
gc_mark_string
gc_trace
gs_gc_reclaim
What each source reports
OSV No score
Heap-buffer-overflow in gc_mark_string
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19780
Crash type: Heap-buffer-overflow READ 4
Crash state:
gc_mark_string
gc_trace
gs_gc_reclaim
- Record
OSV-2020-941- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libspectreOSS-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-2020-941 is a vulnerability with no CVSS score yet in libspectre, published July 22, 2020. No source lists public exploit code. A source reports a fix.