On this page (6 sections)

Debian has published DSA-6600-2, a follow-up to its earlier vim security update, DSA-6600-1. According to the Debian security announcement, the first update did not build correctly into binary packages for the s390x architecture because of test failures during the build. The new update corrects that.

If you run Debian 13 (trixie) servers, especially on s390x, this is worth a quick check. The announcement is short and does not describe the underlying vulnerabilities, so this article sticks to what Debian actually says and how to confirm you are on the corrected package.

What happened

A regression update fixes a problem introduced by an earlier update rather than a new flaw. In this case, Debian says the vim update released in DSA 6600-1 did not produce correct binary packages for s390x, because tests failed during the build. DSA-6600-2 publishes a corrected build.

The announcement does not list CVE identifiers, a severity rating or a description of what DSA-6600-1 contained. For those details, Debian points readers to the vim security tracker page. At the time of writing, only this one Debian announcement was available to us, so nothing here has been independently confirmed by a second source.

What we know and what we do not

Status of key details for DSA-6600-2
DetailStatus
Fixed version for trixie2:9.1.1230-2+deb13u2, stated by Debian
Cause of the regressions390x binary packages not built correctly due to build-time test failures
Debian bug reference1152930
Contents of DSA-6600-1Not described in this announcement
CVE identifiersNot listed in this announcement
CVSS score or severityNot stated
Exploitation in the wildNot stated
Other architectures or releasesNot mentioned in this announcement
Do not assume this is a low-risk or high-risk update. The announcement simply does not say. Check the Debian security tracker for the vulnerabilities covered by the DSA-6600 series.

Who is affected

The announcement names the stable distribution, trixie, and the s390x architecture as the place where the earlier build went wrong. s390x is the architecture used on IBM Z mainframes, so most web servers on x86-64 or ARM are unlikely to have been hit by the broken build itself.

The announcement does not say how other architectures are affected, and it does not describe what DSA-6600-1 fixed. As general patch hygiene rather than anything Debian states here, it is reasonable to confirm the installed vim version on every trixie machine. vim is a common package on administration hosts, jump boxes and shared hosting servers, since it is often the editor people use over SSH.

How to check your exposure

This read-only command prints the installed vim package version and the architecture on Debian. You are looking for a version of 2:9.1.1230-2+deb13u2 or later on trixie.

Show installed vim version and architecture (Debian)Shell
dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' vim

This command shows the Debian release you are running, so you know whether the trixie fixed version applies to you.

Show the Debian release (Debian)Shell
cat /etc/os-release

vim may also be installed under related package names such as vim-tiny or vim-common. This lists any installed packages whose names start with vim so you can see them all.

List installed vim-related packages (Debian)Shell
dpkg -l 'vim*'

What to do now

  1. Identify Debian trixie hosts that have vim installed, including jump boxes and shared servers.
  2. Run the version check above and note any host below 2:9.1.1230-2+deb13u2.
  3. Refresh package lists and upgrade the vim packages through your normal update process.
  4. On s390x hosts, make sure you install the corrected build from DSA-6600-2 rather than relying on the earlier update.
  5. Re-run the version check to confirm the fixed version is installed.
  6. Read the vim page on the Debian security tracker to see which vulnerabilities the DSA-6600 series covers and decide how urgent the rollout is for you.

This updates the package lists and upgrades only the vim package on Debian. It does not restart services, but any open vim sessions keep running the old binary until they are closed.

Update and upgrade the vim package (Debian, run as root or with sudo)Shell
sudo apt update && sudo apt install --only-upgrade vim
Tip. If you manage many servers, use your existing patch tooling to report the installed vim version across the fleet, then compare it with 2:9.1.1230-2+deb13u2.

Monitoring after the update

Regression updates are a reminder to verify rather than assume. After rolling out, check that automatic update tooling on your hosts did not stay on an older build, and keep an eye on the Debian security announcements list for further follow-ups to DSA-6600. Debian's security information page at debian.org/security explains how to apply updates and answers common questions.

For the wider picture of keeping servers and sites patched, our guide on small business website security covers basic routines.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6600-2] vim regression updatelists.debian.org ·
  • Debian
  • vim
  • DSA
  • Linux
  • patching