Debian 13 — libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide

📖 ~4 min read  •  Source: Debian Security Tracker

Related CVEs: CVE-2019-11922 CVE-2021-24031 CVE-2021-24032 CVE-2022-4899

Upstream summary: A race condition in the one-pass compression functions of Zstandard prior to version 1.3.8 could allow an attacker to write bytes out of bounds if an output buffer smaller than the recommended size was used.

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

On Debian 13 hosts running libzstd, administrators observe behaviour consistent with the Debian Security Tracker entry: apt refusing to install or restart affected services, and — for security-rated advisories — exposure to the vulnerability set above. Impact ranges from a single service restart to wider availability incidents whenever libzstd sits on the serving path.

Environment & Reproduction

Reproduction targets Debian 13. Confirm release with cat /etc/debian_version and lsb_release -a, and the currently installed package with dpkg -l libzstd and apt-cache policy libzstd. Capture system state with sudo reportbug libzstd if you need to file upstream. Trigger the workflow that exposes libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide while collecting journalctl -b, /var/log/apt/history.log, and dpkg -l output.

Root Cause Analysis

Root cause is tracked at Debian Security Tracker. The Debian Security Team shipped fixes in the corresponding libzstd point release for Debian 13; running an outdated build leaves the host exposed to the failure modes referenced above. Correlate journalctl --since with apt history (/var/log/apt/history.log) and any kernel taint flags in /proc/sys/kernel/tainted to isolate the originating change.

Quick Triage

Quick triage: systemctl status libzstd, journalctl -u libzstd -n 200, sudo apt update && apt list --upgradable, sudo nft list ruleset (or sudo iptables -L), and sudo dpkg --audit. For kernel issues review journalctl -k --since "1 hour ago".

Step-by-Step Diagnosis

1) systemctl --failed. 2) journalctl -xe and journalctl -u libzstd. 3) Validate firewall: sudo nft list ruleset or sudo iptables -L -n -v. 4) dpkg -V libzstd for integrity. 5) sudo apt install --reinstall libzstd if files were tampered. 6) Correlate findings with /var/log/apt/history.log, /var/log/dpkg.log, and Debian Security Tracker to pin the change that introduced libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide.

Solution – Primary Fix

Primary fix: apply the corrective apt transaction documented in Debian Security Tracker, then reload the affected systemd unit. Typical commands: sudo apt update, sudo apt -y install --only-upgrade libzstd (or sudo unattended-upgrade -v), sudo systemctl daemon-reload, sudo systemctl restart libzstd, then dpkg -l libzstd to validate the new build is installed. For kernel advisories add sudo reboot.

Solution – Alternative Approaches

Alternatives include pinning a known-good version via /etc/apt/preferences.d/libzstd.pref, holding the package with sudo apt-mark hold libzstd, rolling back with sudo apt install libzstd=<old-version>, switching firewall backends between iptables-legacy and nftables via update-alternatives --config iptables, or applying the patch from the security archive only — deb debian-13-security main contrib non-free — while delaying the full point-release upgrade.

Verification & Acceptance Criteria

Acceptance: dpkg -l libzstd shows the expected fixed version, systemctl is-active libzstd is active, journalctl -u libzstd --since "5 minutes ago" shows no errors, apt list --upgradable no longer lists the advisory, sudo nft list ruleset matches the intended policy, and the original reproduction steps for libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide no longer trigger the failure across two consecutive runs.

Rollback Plan

Capture state with apt list --installed > /root/apt-pre.txt and dpkg --get-selections > /root/dpkg-pre.txt. To revert, run sudo apt install --allow-downgrades libzstd=<old-version> and reload systemctl daemon-reload. Reboot if the kernel or initramfs changed and re-verify symptoms. Where LVM snapshots are in use, sudo lvconvert --merge /dev/<vg>/preupgrade is the fastest rollback path.

Prevention & Hardening

Prevent recurrence by enabling unattended-upgrades with Unattended-Upgrade::Origins-Pattern tuned to origin=Debian,codename=${distro_codename},label=Debian-Security, subscribing to debian-security-announce, mirroring through a local apt-mirror or aptly repo for controlled rollouts, version-locking sensitive packages, and monitoring file integrity with debsums -c or aide --check. Apply CIS Debian hardening and keep needrestart installed so service restarts happen automatically after library upgrades.

Related Errors & Cross-Refs

Related issues that commonly surface alongside libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide: apt lock contention (dpkg --configure -a), systemd unit ordering cycles, firewall rule drift, and kernel taint flags in cat /proc/sys/kernel/tainted. See sibling common-problem articles in this Debian 13 series for adjacent failure modes.

View all debian-13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Primary reference: Debian Security Tracker. Supporting docs: Debian Administrators Handbook, man apt, man systemctl, man nft, man iptables, man journalctl, man debsums, the Debian Security Tracker at security-tracker.debian.org, and Debian Security FAQ at debian.org/security/faq. Review /usr/share/doc/libzstd/ for component-level notes implicated in libzstd — multiple vulnerabilities (4 CVEs) — patch and remediation guide.