printk: Fix possible console use-after-free
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fbf9bb81b21537ede387a31cc586f1d2ce66a74e, Kernel 36630cafbeede0b64c370edb2f7b4094327ee1e0, Kernel 8f194dee0c0d1223255bae1429e1939882f540fc and 4 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=c158834b223fbfab3a14855ac203b8d9cddbbefd <fbf9bb81b21537ede387a31cc586f1d2ce66a74e, >=c158834b223fbfab3a14855ac203b8d9cddbbefd <36630cafbeede0b64c370edb2f7b4094327ee1e0, >=c158834b223fbfab3a14855ac203b8d9cddbbefd <8f194dee0c0d1223255bae1429e1939882f540fc, >=c158834b223fbfab3a14855ac203b8d9cddbbefd <f0104a7b730de32eefb3d4a27279592b5504ad59, =6.12 | fbf9bb81b21537ede387a31cc586f1d2ce66a74e, 36630cafbeede0b64c370edb2f7b4094327ee1e0, 8f194dee0c0d1223255bae1429e1939882f540fc, f0104a7b730de32eefb3d4a27279592b5504ad59 |
| linux-kernel: Kernel | >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.12.0 <6.12.110 | 6.18.52, 7.2.6, 6.12.110 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket