CVE-2026-97995

virtio_console: do not free control-out buffers on remove

N/A
Published: September 25, 2026 at 10:23 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: virtio_console: do not free control-out buffers on remove __send_control_msg() publishes &portdev->cpkt as the control-out virtqueue cookie. remove_vqs() walks every virtqueue and passes leftover cookies to free_buf(), which treats them as struct port_buffer and reads sgpages. If a control message is still on c_ovq when the device is unbound, free_buf() reads past the ports_device object. KASAN reported slab-out-of-bounds in free_buf(): free_buf remove_vqs virtcons_remove unbind_store The object was the ports_device allocated in virtcons_probe(). Drain c_ovq without freeing. The packet lives in portdev and is released with it.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16.603.18.1084.1.524.14.394.16.74.174.4.1314.9.9847cb14192bcbba3f15b1c3561e05e084e56fdef66b1c41a0f7183702abb7a104c6c7e196ad69a6b39037306163a6ba5587e4b5ca511ac7be4fb7295ba7a69ec0d8e4a58be7db88d33cbfa2912807bb2ba88e13d9a092fbb772d380944b44eb549ef131fed2bbfac82b7942afc5d8e564d7087835280df495dd807a784fd36f4136516d5858efb6473dda422cf92b16b815efe8207090a9b5a767618fd89542ca
Vendor states this is fixed in 177ee901aa2bab02e7f1f8edbb814fd5e386ed62 (fixed)
Vendor states this is fixed in 2e40c69b9c3448b9c6609cd02013da593b2e123b (fixed)
Vendor states this is fixed in 894f98e73983f37354214a89a3a7fd35bf9e3072 (fixed)
Vendor states this is fixed in 8f6cfc3eca79b8e108d0823756101e2f4f9d811f (fixed)
Vendor states this is fixed in a80c33488e0bbe642ed803b13a4ac8078a70b507 (fixed)
Vendor states this is fixed in b1f39c2a676698cc64c8e105e08b25111a112ec6 (fixed)
Vendor states this is fixed in e03522a990cd2e0f1a736eaa349a9df9ab8541c3 (fixed)
Vendor states this is fixed in f620c40ea6862feed84deb105568b21ec53a7830 (fixed)
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.17 (unaffected)
Affected range stops below 4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card