VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93134: Linux kernel · printk: Fix possible console use-after-free

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fbf9bb81b21537ede387a31cc586f1d2ce66a74e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in fbf9bb81b21537ede387a31cc586f1d2ce66a74e, f0104a7b730de32eefb3d4a27279592b5504ad59, 36630cafbeede0b64c370edb2f7b4094327ee1e0 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to fbf9bb81b21537ede387a31cc586f1d2ce66a74e, f0104a7b730de32eefb3d4a27279592b5504ad59, 36630cafbeede0b64c370edb2f7b4094327ee1e0 or 8f194dee0c0d1223255bae1429e1939882f540fc.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ c158834b223fbfab3a14855ac203b8d9cddbbefd, < fbf9bb81b21537ede387a31cc586f1d2ce66a74e	Fixed in fbf9bb81b21537ede387a31cc586f1d2ce66a74e
LinuxLinux	Affected ≥ c158834b223fbfab3a14855ac203b8d9cddbbefd, < f0104a7b730de32eefb3d4a27279592b5504ad59	Fixed in f0104a7b730de32eefb3d4a27279592b5504ad59
LinuxLinux	Affected ≥ c158834b223fbfab3a14855ac203b8d9cddbbefd, < 36630cafbeede0b64c370edb2f7b4094327ee1e0	Fixed in 36630cafbeede0b64c370edb2f7b4094327ee1e0
LinuxLinux	Affected ≥ c158834b223fbfab3a14855ac203b8d9cddbbefd, < 8f194dee0c0d1223255bae1429e1939882f540fc	Fixed in 8f194dee0c0d1223255bae1429e1939882f540fc
LinuxLinux	Affected =6.12	Fixed in–

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.

References

Community reviews

Loading reviews…