https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:51:27 +0000 https://vulnerability.circl.lu/vuln/cve-2026-93134 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>printk: Fix possible console use-after-free</p> <p>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.</p> <p>Sashiko pointed out that console_flush_one_record() was not doing this.</p> <p>In console_flush_one_record(), after emitting a record, move the further usage of @con after the handover check.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>printk: Fix possible console use-after-free</p> <p>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.</p> <p>Sashiko pointed out that console_flush_one_record() was not doing this.</p> <p>In console_flush_one_record(), after emitting a record, move the further usage of @con after the handover check.</p> https://vulnerability.circl.lu/vuln/cve-2026-93134