On this page (7 sections)
On November 13, 2026, the Debian Security Team published DSA-6628-1, a security update for the Linux kernel in Debian stable (trixie). The advisory bundles fixes for 43 CVE identifiers and says the problems may lead to privilege escalation, denial of service or information leaks.
If you run web servers, VPS instances or hosting nodes on Debian trixie, this update is for you. The advisory does not describe individual bugs or exploitation, so the practical task is simple: install the new kernel and reboot.
What Debian announced
The advisory is short. Debian says several vulnerabilities were found in the Linux kernel and that, for the stable distribution (trixie), they are fixed in version 6.12.117-1. It recommends upgrading the linux packages and points to the Debian security tracker page for linux for per-CVE status. The advisory is tracked under Debian bug 1149377.
Only one publisher covers this story so far, and the advisory itself is the primary source. It gives no CVSS scores, no affected-component breakdown and no statement about attacks in the wild, so severity and exploitation status are unconfirmed. Treat any claim beyond that as unverified until the tracker or upstream records say more.
What the impact categories mean
Debian groups the CVEs under three possible outcomes. The advisory does not say which CVE maps to which outcome, so check the tracker for specifics.
- Privilege escalation: a local user or a compromised service account gains higher rights, potentially root. On a web server this matters most after another weakness, such as a vulnerable web application, gives an attacker a foothold.
- Denial of service: a crash or hang of the kernel or a subsystem, which means downtime for every site on the host.
- Information leaks: kernel memory or data exposed to a process that should not see it, which can help an attacker defeat other protections.
Kernel bugs of this kind often need local access first, though the advisory does not confirm that for each CVE. That is why shared hosting, multi-tenant servers, CI runners and container hosts deserve priority: untrusted code already runs there by design.
Who is affected
The advisory names Debian stable (trixie) and the fixed version 6.12.117-1. Other Debian releases and other distributions are not covered by this advisory, so check their own vendor notices. Cloud images and VPS templates based on trixie are affected if they run an older kernel package and have not been updated.
How to check your exposure
Run these read-only commands on each Debian host. The first shows the kernel currently running; the second lists the installed linux image packages and their versions. Compare the output against 6.12.117-1.
uname -r
dpkg -l 'linux-image*' | grep ^iiThe running kernel can lag behind the installed package until you reboot. If the installed version is current but uname -r shows an older one, the fix is not active yet.
What to do now
- List your Debian trixie hosts and note each one's current kernel version.
- Refresh package lists and upgrade the linux packages (commands below).
- Reboot during a planned window so the new kernel is loaded.
- Confirm with uname -r that the running kernel matches the fixed version.
- Prioritize multi-tenant, shared hosting and container hosts first.
- Review the Debian security tracker page for linux for per-CVE details and any later advisories.
This command updates package lists and installs available upgrades on Debian, including the linux packages. Check the output for the new linux-image version before rebooting.
sudo apt update
sudo apt full-upgradeAfter the reboot, verify the result with the check below. The running kernel should correspond to the fixed release.
uname -r
apt list --installed 2>/dev/null | grep '^linux-image'Detection and monitoring afterwards
The advisory says nothing about exploitation, but a kernel patch is a good moment to review the basics. Check authentication logs for unfamiliar logins, look for unexpected new privileged users or SSH keys, and watch for unplanned reboots or kernel crash messages that could point to denial-of-service attempts.
Kernel patching is one layer. Keep your public-facing stack under watch too: Webforta Monitor tracks uptime, certificate and DNS changes, and the WordPress security checklist covers the application layer that often provides the first foothold.
Timeline
| Date | Event |
|---|---|
| November 13, 2026 | Debian publishes DSA-6628-1 with fixed trixie kernel 6.12.117-1 |
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.
