Debian Corrects Vim Security Package Builds for s390x

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Check Debian 13 trixie systems, especially s390x hosts awaiting the earlier Vim security update. Install 2:9.1.1230-2+deb13u2 from the supported security repository, verify the installed package and architecture, test editing workflows, and retain update evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Debian release, CPU architecture, installed Vim package variants and full package versions, repository configuration, system owners and maintenance groups. Prioritize s390x hosts where the earlier DSA-6600-1 update was unavailable or did not install. Match the distribution and packages to Debian trixie; do not infer the status of other distributions or upstream builds from this notice. Install the updated Vim packages from the supported Debian security repository. Follow Debian package-management guidance and confirm the packages resolve to 2:9.1.1230-2+deb13u2 or a later supported security update for trixie. Verify the complete installed package version and architecture, check package-manager output for held or failed upgrades, and test representative editing, plugins and automation. Restart open editor sessions after saving work so they use the updated executable.

Open the authoritative advisory

Last verified: 2026-11-08 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeVim packages on Debian 13 trixie; s390x security-update delivery
AdvisoryDSA-6600-2
CVEsNo new CVE identifiers are assigned in DSA-6600-2.
Authoritative release dateNovember 8, 2026 at 14:06:18 UTC, as stated in the Debian advisory mailing-list message.
Authority revision dateNo later revision is stated for DSA-6600-2. This advisory follows DSA-6600-1 and corrects its s390x package-build problem.
Affected versionsThe Vim update in DSA-6600-1 did not correctly build binary packages for s390x because of build-time test failures. Debian identifies stable (trixie) for this correction; the notice does not announce a new upstream vulnerability or a new affected-version range.
Fixed versionvim 2:9.1.1230-2+deb13u2 for Debian trixie
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe Debian follow-up does not state malicious exploitation.; no exploitation claim is inferred.

What Changed

DSA-6600-2 corrects a build failure that prevented the preceding Vim security update from producing s390x binary packages. Debian provides replacement trixie packages and recommends upgrading Vim. The follow-up changes the supported fixed package to 2:9.1.1230-2+deb13u2; it does not assign new CVEs.

What To Validate Now

  1. Inventory. Record Debian release, CPU architecture, installed Vim package variants and full package versions, repository configuration, system owners and maintenance groups.
  2. Establish applicability. Prioritize s390x hosts where the earlier DSA-6600-1 update was unavailable or did not install. Match the distribution and packages to Debian trixie; do not infer the status of other distributions or upstream builds from this notice.
  3. Remediate. Install the updated Vim packages from the supported Debian security repository. Follow Debian package-management guidance and confirm the packages resolve to 2:9.1.1230-2+deb13u2 or a later supported security update for trixie.
  4. Validate. Verify the complete installed package version and architecture, check package-manager output for held or failed upgrades, and test representative editing, plugins and automation. Restart open editor sessions after saving work so they use the updated executable.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Preserve the 2: version epoch when comparing Debian packages. A successful repository refresh alone does not prove that the corrected binary package was installed. Coordinate editor restarts to protect unsaved work; this build correction does not establish customer compromise.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.