printk: Fix possible console use-after-free

Answer in brief

CVE-2026-93134 records a Unknown severity vulnerability in printk: Fix possible console use-after-free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=c158834b223fbfab3a14855ac203b8d9cddbbefd <f0104a7b730de32eefb3d4a27279592b5504ad59 \|\| >=c158834b223fbfab3a14855ac203b8d9cddbbefd <fbf9bb81b21537ede387a31cc586f1d2ce66a74e \|\| >=c158834b223fbfab3a14855ac203b8d9cddbbefd <8f194dee0c0d1223255bae1429e1939882f540fc \|\| >=c158834b223fbfab3a14855ac203b8d9cddbbefd <36630cafbeede0b64c370edb2f7b4094327ee1e0	f0104a7b730de32eefb3d4a27279592b5504ad59, fbf9bb81b21537ede387a31cc586f1d2ce66a74e, 8f194dee0c0d1223255bae1429e1939882f540fc, 36630cafbeede0b64c370edb2f7b4094327ee1e0
Linux/Linuxgeneric	6.12	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f0104a7b730de32eefb3d4a27279592b5504ad59 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: printk: Fix possible console use-after-free When emitting a record via legacy printing, it is possible that a handover to another legacy printing context occurs. When a context has performed a handover, the console SRCU read lock is released and the pointer to the console struct might now be invalid. Therefore, after calling nbcon_legacy_emit_next_record() or console_emit_next_record(), it is necessary to check if a handover occurred _before_ further @con usage. Sashiko pointed out that console_flush_one_record() was not doing this. In console_flush_one_record(), after emitting a record, move the further usage of @con after the handover check.

Quoted source text, attributed separately from HOL analysis.