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

> A use-after-free in the Linux kernel console handling allows local attackers to potentially execute code or escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93134, DEBIAN-CVE-2026-93134, GHSA-hf69-jx63-p85x, UBUNTU-CVE-2026-93134

## What is CVE-2026-93134?

CVE-2026-93134 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93134?


## How do I fix CVE-2026-93134?

Apply the vendor's patch.

## Is CVE-2026-93134 being exploited?

There is no known exploitation of CVE-2026-93134 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93134 and fix it if it is affected.

What it is: CVE-2026-93134 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93134 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93134/ (Markdown: https://insights.sbomify.com/CVE-2026-93134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93134
- OSV: https://osv.dev/vulnerability/CVE-2026-93134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93134/
Summaries are generated and may contain mistakes; the official description above is the record.