Debian trixie, Debian bookworm: control privileged access

At a glance

Debian trixie, Debian bookworm: privilege escalation. This 2026-05-23 case examines 2 version entries and 6 CVEs, documented releases and checks suited to runtime platforms, using CERTFR-2026-AVI-0637.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-05-23, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0637, published on 2026-05-22. Its scope includes Debian trixie, Debian bookworm. Reported consequences are denial of service, loss of confidentiality, privilege escalation. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 2 version entries; CVE identifier count: 6. Track remediation by component: a successful overall update does not demonstrate that Debian trixie and Debian bookworm each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-0637
Source first published
2026-05-22
Latest source revision available for this day
2026-05-22
Named components
Debian trixie, Debian bookworm
CVE identifiers
CVE-2026-43220, CVE-2026-43490, CVE-2026-46333, CVE-2026-43109, CVE-2026-31499, CVE-2026-43088
ComponentPublished condition
Debian trixie< 6.12.88-1.
Debian bookworm< 6.1.172-1.

For Debian trixie, the published condition is “< 6.12.88-1.”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Debian trixie, Debian bookworm does not close this case.

Mechanism and prerequisites

Privilege escalation expands an existing foothold into greater permissions. Examine boundaries between ordinary accounts, services and administrators, and retain evidence of role changes.

The primary record CVE-2026-43220, published by Linux, covers Linux. The retained revision is dated 2026-05-17. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0637.

Choose the appropriate intervention

  1. Locate Debian trixie instances, running releases and service owners. Record condition < 6.12.88-1. in the ticket alongside reference CERTFR-2026-AVI-0637.
  2. Compare the installed branch with the vendor’s Debian trixie release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Debian trixie, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Debian trixie, Debian bookworm: For Debian trixie, capture the version loaded by the process or active kernel, then restart only as required by maintenance instructions. Check a dependent workflow and look for embedded copies in distributed images or executables. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0637: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Debian trixie?

Advisory CERTFR-2026-AVI-0637 states: Debian trixie — < 6.12.88-1.. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for Debian trixie and Debian bookworm?

CERTFR-2026-AVI-0637 distinguishes these components within a scope containing 2 entries. Match each branch to its own update documentation and functional check.

What is still needed to assess Debian trixie, Debian bookworm exposure?

For Debian trixie, Debian bookworm, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0637 do not establish every prerequisite or active exploitation.

Sources and related reading

Practical guide : Prioritize vulnerabilities and verify remediation

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0637
Advisory revision : · Checked on :

Affected systems · 2

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Debian trixie versions antérieures à 6.12.88-1.
  2. Debian bookworm versions antérieures à 6.1.172-1.
CVE identifiers · 6