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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
c158834b223fbfab3a14855ac203b8d9cddbbefd to < f0104a7b730de32eefb3d4a27279592b5504ad59affectedc158834b223fbfab3a14855ac203b8d9cddbbefd to < fbf9bb81b21537ede387a31cc586f1d2ce66a74eaffectedc158834b223fbfab3a14855ac203b8d9cddbbefd to < 8f194dee0c0d1223255bae1429e1939882f540fcaffectedc158834b223fbfab3a14855ac203b8d9cddbbefd to < 36630cafbeede0b64c370edb2f7b4094327ee1e0affected
Linux Linux
Default version status: affected
6.12affected0 to < 6.12unaffected6.12.110 to ≤ 6.12.*unaffected6.18.52 to ≤ 6.18.*unaffected7.2.6 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected