Most recent entries from all

cnvd-2021-78755

2026-10-19T23:00:15.507032+00:00

cnvd-2021-78755

EUVD-2026-48199

2026-10-19T23:00:15.507085+00:00

EUVD-2026-48199

fkie_cve-2020-36440

2026-10-19T23:00:15.507099+00:00

An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder, it implements Send for any R: Read.

GHSA-f6g6-54hm-fhxv — Data races in libsbc

2026-10-19T23:00:15.507130+00:00

Affected: crates.io: libsbc

Affected versions of this crate implements `Send` for `Decoder` for any `R: Read`. This allows `Decoder` to contain `R: !Send` and carry (move) it to another thread.

This can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.

The flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder`.

gsd-2020-36440

2026-10-19T23:00:15.507158+00:00

gsd-2020-36440

RUSTSEC-2020-0120 — `Decoder` can carry `R: !Send` to other threads

2026-10-19T23:00:15.507170+00:00

Affected: crates.io: libsbc

Affected versions of this crate implements `Send` for `Decoder` for any `R: Read`. This allows `Decoder` to contain `R: !Send` and carry (move) it to another thread.

This can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.

The flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder`.