CVE-2026-93134

printk: Fix possible console use-after-free

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Linux kernel bug allows a console use‑after‑free when a legacy printing handover occurs while a console buffer is still in use. After the handover the console SRCU read lock is released, the console struct pointer may become invalid, and subsequent access can dereference freed memory. This flaw can lead to memory corruption or a system crash.

Affected Systems

The vulnerability resides in the Linux kernel itself and affects any system that uses the legacy console printing infrastructure. No specific kernel versions are listed in the CNA information, so the issue may exist across multiple releases until the patch is applied.

Risk and Exploitability

The EPSS score for this vulnerability is below 1%, indicating a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, suggesting it is not part of known actively exploited vulnerabilities. Therefore, the overall risk assessment is low, though environments that rely on legacy console printing remain vulnerable to a use‑after‑free that could cause memory corruption or a system crash once the handover occurs.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check for and apply the latest kernel patch that introduces handover checks before accessing the console structure.
  • If a patch is not yet available, consider disabling legacy console printing or redirecting kernel log output to avoid triggering the handover condition.
  • Monitor system logs for unexpected kernel panics or crashes that may indicate an unpatched use‑after‑free scenario.

Generated by OpenCVE AI on September 19, 2026 at 07:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
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.
Title printk: Fix possible console use-after-free
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 9:06 AM
Reserved
Sep 17, 2026, 4:02 PM
Status
Received
Published
Sep 17, 2026, 5:18 PM
Modified
Oct 19, 2026, 10:17 AM