Vulnerability 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
- https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0
- https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc
- https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59
- https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e
FAQ
What is CVE-2026-93134?
CVE-2026-93134 is a documented vulnerability. 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 ...
How severe is CVE-2026-93134?
CVSS scoring is not yet available for CVE-2026-93134. Check NVD for updates.
Is there a patch for CVE-2026-93134?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.