printk: Fix possible console use-after-free
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From c158834b223fbfab3a14855ac203b8d9cddbbefd · fixed in f0104a7b730de32eefb3d4a27279592b5504ad59; From c158834b223fbfab3a14855ac203b8d9cddbbefd · fixed in fbf9bb81b21537ede387a31cc586f1d2ce66a74e; From c158834b223fbfab3a14855ac203b8d9cddbbefd · fixed in 8f194dee0c0d1223255bae1429e1939882f540fc; From c158834b223fbfab3a14855ac203b8d9cddbbefd · fixed in 36630cafbeede0b64c370edb2f7b4094327ee1e0
- Linux Linux
6.12
- KernelLinux
From 6.12.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6