OSV-2017-97
Use-after-poison in rawspeed::unroll_loop_t<void rawspeed::LJpegDecompressor::decodeN<4>
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4451
Crash type: Use-after-poison WRITE 2
Crash state:
rawspeed::unroll_loop_t<void rawspeed::LJpegDecompressor::decodeN<4>
void rawspeed::LJpegDecompressor::decodeN<4>
rawspeed::AbstractLJpegDecompressor::decode
What each source reports
OSV No score
Use-after-poison in rawspeed::unroll_loop_t<void rawspeed::LJpegDecompressor::decodeN<4>
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4451
Crash type: Use-after-poison WRITE 2
Crash state:
rawspeed::unroll_loop_t<void rawspeed::LJpegDecompressor::decodeN<4>
void rawspeed::LJpegDecompressor::decodeN<4>
rawspeed::AbstractLJpegDecompressor::decode
- Record
OSV-2017-97- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
librawspeedOSS-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-2017-97 is a vulnerability with no CVSS score yet in librawspeed, published January 13, 2021. No source lists public exploit code. A source reports a fix.