{"id":"CVE-2026-93134","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When …","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= c158834b223fbfab3a14855ac203b8d9cddbbefd < f0104a7b730de32eefb3d4a27279592b5504ad59","Linux >= c158834b223fbfab3a14855ac203b8d9cddbbefd < fbf9bb81b21537ede387a31cc586f1d2ce66a74e","Linux >= c158834b223fbfab3a14855ac203b8d9cddbbefd < 8f194dee0c0d1223255bae1429e1939882f540fc","Linux >= c158834b223fbfab3a14855ac203b8d9cddbbefd < 36630cafbeede0b64c370edb2f7b4094327ee1e0","Linux 6.12"],"published":"2026-09-17","updated":"2026-09-17","sourceUpdated":"2026-09-17T17:18:08.260","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-93134","references":[{"url":"https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-17T16:21:47.746Z","epss":0.002,"epssPercentile":0.10106,"slug":"CVE-2026-93134","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When a context has performed a\nhandover, the console SRCU read lock is released and the pointer to the\nconsole struct might now be invalid. Therefore, after calling\nnbcon_legacy_emit_next_record() or console_emit_next_record(), it is\nnecessary to check if a handover occurred _before_ further @con usage.\n\nSashiko pointed out that console_flush_one_record() was not doing this.\n\nIn console_flush_one_record(), after emitting a record, move the further\nusage of @con after the handover check.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}