CVE-2019-16137 · cross-distro fix matrix

CVE-2019-16137: An issue was discovered in the spin crate before 0.5.2 for Rust, when RwLock is used. Because memory ordering is mishandled, two writers can acquire the lock at the same time, violating mutual exclusion.

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2019-16137 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

rust-spin→ fixed in0.5.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rust-spin
```

Debian bookworm

Source: Debian Security Tracker

rust-spin→ fixed in0.5.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rust-spin
```

Debian trixie

Source: Debian Security Tracker

rust-spin→ fixed in0.5.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rust-spin
```

Are YOU affected by CVE-2019-16137?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2019-16137dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)