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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-93134)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-93134)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
468370	Google: sys-kernel/cchost-kernel-6_12, sys-kernel/csql-kernel-6_12, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_12: security update to 19216.700.7	Tenable Cloud Security	Google COS Security Checks	Local	high
468370	Google: sys-kernel/cchost-kernel-6_12, sys-kernel/csql-kernel-6_12, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_12: security update to 19216.700.7	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
347670	Linux Distros Unpatched Vulnerability : CVE-2026-93134	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-93134

high

Tenable Plugins

high

high

high

high

high