Debian Updates the Linux 6.12 Kernel for Bookworm

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

Quick Answer

On Debian 12 systems using linux-6.12, install 6.12.117-1~deb12u1 or the supported superseding security package, then verify the corrected kernel is running.

Confirm Scope And Apply The Supported Remediation

What to do now: Record the Debian release, installed kernel package family, active kernel, boot configuration, out-of-tree modules and service owner. Confirm the system uses the linux-6.12 package family named by DLA-4927-1. Assess hardware and workload dependencies before applying the update; presence of a Linux host alone does not establish applicability. Install the updated Debian packages from supported repositories and schedule a controlled reboot into the corrected kernel. Preserve a tested boot and recovery path appropriate to the host. Verify the running kernel after restart, boot logs, storage and network connectivity, required modules and representative services. Retain package records, reboot evidence and application validation results.

Open the authoritative advisory

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

Scope And Authority

Product scopeDebian 12 (bookworm) linux-6.12 packages
AdvisoryDLA-4927-1
CVEsCVE-2026-100080, CVE-2026-100081, CVE-2026-100082, CVE-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, CVE-2026-99290, CVE-2026-99292, CVE-2026-99295, CVE-2026-99296, CVE-2026-99297, CVE-2026-99298, CVE-2026-99299, CVE-2026-99300, CVE-2026-99301, CVE-2026-99302, CVE-2026-99303, CVE-2026-99304, CVE-2026-99305, CVE-2026-99306, CVE-2026-99307, CVE-2026-99309, CVE-2026-99310, CVE-2026-99311, CVE-2026-99323, CVE-2026-99324, CVE-2026-99327, CVE-2026-99328, CVE-2026-99330, CVE-2026-99331, CVE-2026-99332, CVE-2026-99333, CVE-2026-99334, CVE-2026-99339, CVE-2026-99340, CVE-2026-99341, CVE-2026-99342, CVE-2026-99343, CVE-2026-99344, CVE-2026-99346, CVE-2026-99351, CVE-2026-99352, CVE-2026-99353, CVE-2026-99354, CVE-2026-99355, CVE-2026-99356, CVE-2026-99357, CVE-2026-99358, CVE-2026-99359, CVE-2026-99360, CVE-2026-99361, CVE-2026-99362, CVE-2026-99364, CVE-2026-99365, CVE-2026-99366, CVE-2026-99367, CVE-2026-99368, CVE-2026-99370, CVE-2026-99371, CVE-2026-99372, CVE-2026-99375, CVE-2026-99378, CVE-2026-99385, CVE-2026-99386, CVE-2026-99388, CVE-2026-99389, CVE-2026-99390, CVE-2026-99392, CVE-2026-99393, CVE-2026-99395, CVE-2026-99396, CVE-2026-99397, CVE-2026-99398, CVE-2026-99399, CVE-2026-99400, CVE-2026-99403, CVE-2026-99404, CVE-2026-99405, CVE-2026-99406, CVE-2026-99407, CVE-2026-99408, CVE-2026-99409, CVE-2026-99410, CVE-2026-99413, CVE-2026-99414, CVE-2026-99415, CVE-2026-99416, CVE-2026-99417, CVE-2026-99418, CVE-2026-99419, CVE-2026-99420, CVE-2026-99421, CVE-2026-99422, CVE-2026-99423, CVE-2026-99424, CVE-2026-99425, CVE-2026-99427, CVE-2026-99428, CVE-2026-99429, CVE-2026-99430, CVE-2026-99431, CVE-2026-99432, CVE-2026-99433, CVE-2026-99434, CVE-2026-99435, CVE-2026-99436, CVE-2026-99437, CVE-2026-99438, CVE-2026-99439, CVE-2026-99440, CVE-2026-99441, CVE-2026-99442, CVE-2026-99444, CVE-2026-99446, CVE-2026-99448, CVE-2026-99449, CVE-2026-99451, CVE-2026-99452, CVE-2026-99453, CVE-2026-99454, CVE-2026-99455, CVE-2026-99456, CVE-2026-99460, CVE-2026-99461, CVE-2026-99463, CVE-2026-99464, CVE-2026-99465, CVE-2026-99466, CVE-2026-99467, CVE-2026-99468, CVE-2026-99469, CVE-2026-99470, CVE-2026-99471, CVE-2026-99473, CVE-2026-99474, CVE-2026-99475, CVE-2026-99477, CVE-2026-99479, CVE-2026-99480, CVE-2026-99481, CVE-2026-99482, CVE-2026-99483, CVE-2026-99488, CVE-2026-99489, CVE-2026-99490, CVE-2026-99491, CVE-2026-99492, CVE-2026-99494, CVE-2026-99497, CVE-2026-99503, CVE-2026-99505, CVE-2026-99506, CVE-2026-99507, CVE-2026-99508, CVE-2026-99509, CVE-2026-99510, CVE-2026-99511, CVE-2026-99512, CVE-2026-99513, CVE-2026-99514, CVE-2026-99515, CVE-2026-99516, CVE-2026-99521, CVE-2026-99525, CVE-2026-99526, CVE-2026-99528, CVE-2026-99529, CVE-2026-99531, CVE-2026-99532, CVE-2026-99534, CVE-2026-99535, CVE-2026-99537, CVE-2026-99538, CVE-2026-99539, CVE-2026-99540, CVE-2026-99541, CVE-2026-99542, CVE-2026-99543, CVE-2026-99544, CVE-2026-99545, CVE-2026-99546, CVE-2026-99547, CVE-2026-99548, CVE-2026-99549, CVE-2026-99550, CVE-2026-99551, CVE-2026-99552, CVE-2026-99554, CVE-2026-99555, CVE-2026-99556, CVE-2026-99557, CVE-2026-99558, CVE-2026-99561, CVE-2026-99565, CVE-2026-99799, CVE-2026-99804
Authoritative release date2026-11-21T22:14:06Z — timestamp in the signed Debian LTS announcement (23:14:06 +0100).
Authority revision dateNo separate material revision is stated for this release.
Affected versionsDebian 12 (bookworm) linux-6.12 packages before 6.12.117-1~deb12u1. The advisory does not establish applicability to other Debian releases or kernel package families.
Fixed versionlinux-6.12 6.12.117-1~deb12u1 for Debian 12 (bookworm).
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not state that these vulnerabilities are being exploited in the wild.; no exploitation claim is inferred.

What Changed

Debian issued DLA-4927-1 for Linux 6.12 vulnerabilities that may permit privilege escalation, denial of service or information disclosure. The package also incorporates fixes from upstream stable updates 6.12.116 and 6.12.117.

What To Validate Now

  1. Inventory. Record the Debian release, installed kernel package family, active kernel, boot configuration, out-of-tree modules and service owner.
  2. Establish applicability. Confirm the system uses the linux-6.12 package family named by DLA-4927-1. Assess hardware and workload dependencies before applying the update; presence of a Linux host alone does not establish applicability.
  3. Remediate. Install the updated Debian packages from supported repositories and schedule a controlled reboot into the corrected kernel. Preserve a tested boot and recovery path appropriate to the host.
  4. Validate. Verify the running kernel after restart, boot logs, storage and network connectivity, required modules and representative services. Retain package records, reboot evidence and application validation results.
  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

Plan redundancy and maintenance windows for hosts whose reboot affects service availability. Debian publishes no CVSS score or exploitation statement in this advisory; the broad CVE list is not evidence that every vulnerable path is reachable on each host.

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.