Debian Updates the Trixie Linux Kernel for 43 Vulnerabilities

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

Quick Answer

Update Debian trixie linux packages to 6.12.117-1 and reboot into the corrected kernel under an approved maintenance plan. Validate services and external modules before broad rollout.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify Debian trixie hosts, installed and running kernel versions, architecture, kernel-dependent workloads and external modules. Map each CVE to the actual kernel configuration. Do not extend this package fix to other Debian releases or separately maintained kernels. Install the supported Debian security packages and ensure the corrected kernel is active; plan a reboot and retain a tested recovery option. Record package versions and the active kernel after reboot. Test networking, storage, drivers, critical applications and monitoring; retain boot and workload evidence.

Open the authoritative advisory

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

Scope And Authority

Product scopeDebian 13 trixie Linux kernel packages
AdvisoryDSA-6628-1
CVEsCVE-2026-89866, CVE-2026-92499, CVE-2026-98176, CVE-2026-98177, CVE-2026-98180, CVE-2026-98228, CVE-2026-98408, CVE-2026-98439, CVE-2026-98449, CVE-2026-98466, CVE-2026-98674, CVE-2026-98682, CVE-2026-98683, CVE-2026-98684, CVE-2026-98685, CVE-2026-98714, CVE-2026-98715, CVE-2026-98786, CVE-2026-98853, CVE-2026-98863, CVE-2026-98920, CVE-2026-98978, CVE-2026-98989, CVE-2026-98996, CVE-2026-99021, CVE-2026-99026, CVE-2026-99076, CVE-2026-99086, CVE-2026-99087, CVE-2026-99109, CVE-2026-99122, CVE-2026-99146, CVE-2026-99172, CVE-2026-99270, CVE-2026-99271, CVE-2026-99273, CVE-2026-99274, CVE-2026-99281, CVE-2026-99282, CVE-2026-99283, CVE-2026-99286, CVE-2026-99287, CVE-2026-99288
Authoritative release date2026-11-13T21:19:06Z — Debian announcement message timestamp.
Authority revision dateNo separate material revision date is provided by the authority.
Affected versionsDebian trixie linux packages before 6.12.117-1. Individual vulnerability applicability depends on architecture, enabled kernel components and local configuration.
Fixed versionDebian trixie linux packages 6.12.117-1.
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusDebian does not confirm exploitation in the wild in this advisory.; no exploitation claim is inferred.

What Changed

Debian fixes 43 Linux kernel CVEs that can result in privilege escalation, denial of service or information disclosure. The advisory supplies the corrected package for Debian trixie.

What To Validate Now

  1. Inventory. Identify Debian trixie hosts, installed and running kernel versions, architecture, kernel-dependent workloads and external modules.
  2. Establish applicability. Map each CVE to the actual kernel configuration. Do not extend this package fix to other Debian releases or separately maintained kernels.
  3. Remediate. Install the supported Debian security packages and ensure the corrected kernel is active; plan a reboot and retain a tested recovery option.
  4. Validate. Record package versions and the active kernel after reboot. Test networking, storage, drivers, critical applications and monitoring; retain boot and workload evidence.
  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

Kernel package installation alone does not replace running kernel code. Coordinate availability and external-module compatibility; preserve rollback media and follow local change procedures.

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.