virtio_console: do not free control-out buffers on remove
Summary
| CVE | CVE-2026-97995 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:27 UTC |
| Updated | 2026-09-25 11:17:27 UTC |
| 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.054160000 (date 2026-09-26)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected a7a69ec0d8e4a58be7db88d33cbfa2912807bb2b 177ee901aa2bab02e7f1f8edbb814fd5e386ed62 git | Not specified |
| CNA | Linux | Linux | affected a7a69ec0d8e4a58be7db88d33cbfa2912807bb2b a80c33488e0bbe642ed803b13a4ac8078a70b507 git | Not specified |
| CNA | Linux | Linux | affected a7a69ec0d8e4a58be7db88d33cbfa2912807bb2b f620c40ea6862feed84deb105568b21ec53a7830 git | Not specified |
| CNA | Linux | Linux | affected a7a69ec0d8e4a58be7db88d33cbfa2912807bb2b 894f98e73983f37354214a89a3a7fd35bf9e3072 git | Not specified |
| CNA | Linux | Linux | affected f92b16b815efe8207090a9b5a767618fd89542ca git | Not specified |
| CNA | Linux | Linux | affected d2bbfac82b7942afc5d8e564d7087835280df495 git | Not specified |
| CNA | Linux | Linux | affected a88e13d9a092fbb772d380944b44eb549ef131fe git | Not specified |
| CNA | Linux | Linux | affected dd807a784fd36f4136516d5858efb6473dda422c git | Not specified |
| CNA | Linux | Linux | affected 47cb14192bcbba3f15b1c3561e05e084e56fdef6 git | Not specified |
| CNA | Linux | Linux | affected 6b1c41a0f7183702abb7a104c6c7e196ad69a6b3 git | Not specified |
| CNA | Linux | Linux | affected 9037306163a6ba5587e4b5ca511ac7be4fb7295b git | Not specified |
| CNA | Linux | Linux | affected 3.16.60 3.17 semver | Not specified |
| CNA | Linux | Linux | affected 3.18.108 3.19 semver | Not specified |
| CNA | Linux | Linux | affected 4.1.52 4.2 semver | Not specified |
| CNA | Linux | Linux | affected 4.4.131 4.5 semver | Not specified |
| CNA | Linux | Linux | affected 4.9.98 4.10 semver | Not specified |
| CNA | Linux | Linux | affected 4.14.39 4.15 semver | Not specified |
| CNA | Linux | Linux | affected 4.16.7 4.17 semver | Not specified |
| CNA | Linux | Linux | affected 4.17 | Not specified |
| CNA | Linux | Linux | unaffected 4.17 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/f620c40ea6862feed84deb105568b21ec53a7830 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a80c33488e0bbe642ed803b13a4ac8078a70b507 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/894f98e73983f37354214a89a3a7fd35bf9e3072 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/177ee901aa2bab02e7f1f8edbb814fd5e386ed62 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.