Strix
63.5K

CVE-2026-93134

Unknown

Last modified

CVE-2026-93134 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= c158834b223fbfab3a14855ac203b8d9cddbbefd, < f0104a7b730de32eefb3d4a27279592b5504ad59; >= c158834b223fbfab3a14855ac203b8d9cddbbefd, < fbf9bb81b21537ede387a31cc586f1d2ce66a74e; >= c158834b223fbfab3a14855ac203b8d9cddbbefd, < 8f194dee0c0d1223255bae1429e1939882f540fc; >= c158834b223fbfab3a14855ac203b8d9cddbbefd, < 36630cafbeede0b64c370edb2f7b4094327ee1e0
LinuxLinux6.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93134?
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.
How severe is CVE-2026-93134?
Severity scoring for CVE-2026-93134 is pending analysis.
How do I fix CVE-2026-93134?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93134?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST