Debian 12 — bash-completion — vulnerability — patch and remediation guide

📖 ~4 min read  •  Source: Debian Security Tracker

Related CVEs: CVE-2018-7738

Upstream summary: In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

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

bash-completion ships data files, not a daemon — nothing on Debian 12 listens on a socket because it is installed. The exposure lives in whatever reads those files: a font engine parsing glyph tables, a TLS library consulting the trust store, a runtime resolving a zone name. Symptoms are therefore indirect — a renderer or PDF job crashing on a malformed face, certificate validation accepting or rejecting the wrong issuer, timestamps and scheduled work landing an hour out after a rule change. Long-running processes keep the old copy cached until they are restarted. bash-completion is a package of static data — fonts, certificates, timezone rules or documentation — read by other programs, so it has no unit of its own to restart; the restarts that matter belong to its consumers.

Environment & Reproduction

Reproduction targets Debian 12 (bookworm). Confirm release and installed package:

cat /etc/debian_version
lsb_release -a 2>/dev/null || cat /etc/os-release
dpkg -l bash-completion | tail -2
apt-cache policy bash-completion
dpkg-query -W -f='${Status}\n' bash-completion

Exercise the workload that uses bash-completion while collecting:

needrestart -b -r l  # (pkg: needrestart) run as root; machine-readable. NEEDRESTART-SVC = units still mapping deleted libs, NEEDRESTART-SESS = login sessions, NEEDRESTART-KSTA = kernel state. -r l never restarts anything
needrestart -v -l -r l  # human-readable, libraries only (-l); names each PID and the obsolete file it still maps
checkrestart -v  # (pkg: debian-goodies) older alternative; add -p to report only deleted files owned by a dpkg package, -m for machine-readable
sudo journalctl -xe --no-pager | tail -200
sudo tail -200 /var/log/apt/history.log
sudo tail -200 /var/log/dpkg.log

Root Cause Analysis

Root cause is tracked at Debian Security Tracker. The Debian Security Team shipped fixes in the corresponding bash-completion point release for Debian 12 (suite bookworm-security); running an outdated build leaves the host exposed to the failure modes referenced above. Correlate apt history with the journal:

grep -A2 -B2 bash-completion /var/log/apt/history.log
zgrep -A2 -B2 bash-completion /var/log/apt/history.log.*.gz 2>/dev/null
cat /proc/sys/kernel/tainted   # non-zero = tainted kernel / out-of-tree modules

Quick Triage

Run these on Debian 12 to capture the current state of bash-completion:

dpkg -l bash-completion | tail -1                   # installed version
dpkg -V bash-completion                              # verify shipped files
sudo apt update && apt list --upgradable 2>/dev/null | grep -i security
systemctl --failed --no-pager
sudo nft list ruleset 2>/dev/null | head -50
sudo aa-status 2>/dev/null | head -20      # AppArmor profiles
dpkg-query -L bash-completion 2>/dev/null | grep -E '^/etc/init\.d/[^/]+$'  # legacy SysV init script; its basename is the service name for 'service <name> restart' on non-systemd hosts
systemctl list-unit-files --no-pager --type=service,socket,timer | grep -iF -- 'bash-completion'  # fuzzy name match; -F is required because package names contain regex metacharacters ('+' in libstdc++6/g++-13 makes -E fail to match at all)

Step-by-Step Diagnosis

1. List failed systemd units.

   systemctl --failed --no-pager

2. Tail the journal for bash-completion and the system bus.

   sudo journalctl -xe -f --no-pager

3. Inspect firewall state (this OS defaults to nftables).

   sudo nft list ruleset
   sudo nft list tables

4. Verify bash-completion file integrity and reinstall if anything is altered.

   sudo dpkg -V bash-completion
   sudo debsums -c bash-completion 2>/dev/null
   sudo apt install --reinstall -y bash-completion

5. Check AppArmor denials (Debian 11+ default-enabled).

   sudo journalctl -k | grep -i 'apparmor="DENIED"' | tail -30
   sudo aa-status | grep -i bash

6. Correlate findings with /var/log/apt/history.log, /var/log/dpkg.log, and Debian Security Tracker to pin the change that introduced the regression.

Solution – Primary Fix

Apply the corrective apt transaction documented in Debian Security Tracker from the security suite, then reload the affected unit:

sudo apt update
sudo apt -y install --only-upgrade bash-completion
# Unit name may differ from package name; check first:
systemctl daemon-reexec  # REQUIRED after a systemd / libsystemd upgrade: re-execs PID 1 against the new library without rebooting (needrestart flags this as 'systemd-manager')
needrestart -r i  # (pkg: needrestart) interactive: prompts per service. The safe default on a production box
needrestart -r a  # non-interactive: restarts EVERY flagged unit. Maintenance window only -- it will bounce databases and web servers without asking
dpkg -l bash-completion | tail -1                # confirm new version

For kernel / glibc / systemd / openssl advisories a reboot is required:

sudo apt install -y needrestart
sudo needrestart -r l       # list services that need restart
sudo systemctl reboot       # or: sudo shutdown -r now

Solution – Alternative Approaches

If the primary upgrade is not viable, pick from these:

• Pin a known-good version via apt preferences:

  # /etc/apt/preferences.d/bash-completion.pref
  Package: bash-completion
  Pin: version <good-version>
  Pin-Priority: 1001

• Mark the package on hold so apt cannot upgrade it:

  sudo apt-mark hold bash-completion
  apt-mark showhold | grep bash-completion
  # Release the hold later with:
  sudo apt-mark unhold bash-completion

• Downgrade to an older NVR if a regression is suspected:

  apt-cache madison bash-completion
  sudo apt install --allow-downgrades -y bash-completion=<older-version>

• Switch firewall backend between iptables-legacy and nftables (Debian 10+):

  sudo update-alternatives --config iptables
  sudo update-alternatives --config ip6tables
  sudo systemctl restart netfilter-persistent 2>/dev/null

• Take only the security archive update and defer the full point-release upgrade:

  # /etc/apt/sources.list.d/bookworm-security-only.list
  deb http://security.debian.org/debian-security bookworm-security main contrib non-free
  # then:
  sudo apt update && sudo apt -y install --only-upgrade -t bookworm-security bash-completion

• Investigate AppArmor blocking the new binary; switch the profile to complain mode briefly:

  # reproduce, capture denials, then re-enforce:

Verification & Acceptance Criteria

All of these should pass after the fix is applied:

dpkg -l bash-completion | tail -1                                  # expected fixed version
apt list --upgradable 2>/dev/null | grep -i security || echo OK
sudo nft list ruleset | head
sudo aa-status 2>/dev/null | head -5

The conditions described in the advisory must no longer be reported for bash-completion across two consecutive runs.

Rollback Plan

Capture state before any change:

apt list --installed 2>/dev/null > /root/apt-pre.txt
dpkg --get-selections > /root/dpkg-pre.txt
# LVM snapshot of the root LV (only if root sits on LVM):
sudo lvcreate -L 4G -s -n root_pre_patch /dev/<vg>/<root-lv>

To revert:

sudo apt install --allow-downgrades -y bash-completion=<old-version>
# If a kernel was rolled back, reboot and select the previous kernel from GRUB:
sudo systemctl reboot
# LVM snapshot merge (offline / on next reboot):
sudo lvconvert --merge /dev/<vg>/root_pre_patch

Prevention & Hardening

Reduce the chance of this recurring on Debian 12:

• Enable scheduled security updates via unattended-upgrades:

  sudo apt install -y unattended-upgrades apt-listchanges
  sudo dpkg-reconfigure -plow unattended-upgrades
  # /etc/apt/apt.conf.d/50unattended-upgrades:
  Unattended-Upgrade::Origins-Pattern { "origin=Debian,codename=${distro_codename},label=Debian-Security"; };

• Install needrestart so services restart automatically after library upgrades:

  sudo apt install -y needrestart
  # /etc/needrestart/needrestart.conf -> $nrconf{restart} = 'a';

• Subscribe to debian-security-announce and watch security-tracker.debian.org.

• Mirror locally for controlled rollouts:

  sudo apt install -y apt-mirror
  # /etc/apt/mirror.list:
  deb http://deb.debian.org/debian bookworm main contrib non-free
  deb http://security.debian.org/debian-security bookworm-security main contrib non-free
  sudo apt-mirror

• Monitor file integrity with debsums and AIDE:

  sudo apt install -y debsums aide
  sudo debsums -ca           # report only changed conffile-less files
  sudo aideinit && sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
  sudo aide --check

• Apply CIS Debian Linux Benchmark hardening and review auditd rules in /etc/audit/rules.d/.

Related Errors & Cross-Refs

Issues that commonly surface alongside a bash-completion update: apt lock contention, broken dpkg state, systemd ordering cycles, AppArmor denials, and firewall rule drift. Useful triage:

sudo dpkg --configure -a
sudo apt --fix-broken install
systemd-analyze critical-chain
sudo journalctl -k | grep -i apparmor | tail
cat /proc/sys/kernel/tainted

View all debian-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Primary reference: Debian Security Tracker. Manual pages useful on Debian 12:

man apt
man apt-get
man apt-mark
man dpkg
man systemctl
man journalctl
man nft
man apparmor
man unattended-upgrades

Other resources: The Debian Administrator’s Handbook, Debian Security FAQ, Debian Security Tracker, and per-package notes in /usr/share/doc/bash-completion/ for components implicated in this advisory.