CVE-2026-97986

virtio_input: stop callbacks before unregistering input device

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_input: stop callbacks before unregistering input device virtinput_remove() unregisters the input device before resetting the virtio device. virtinput_recv_events() drops vi->lock around input_event(), so clearing vi->ready does not stop a callback that passed the entry check. It can still use vi->idev, requeue buffers and kick the queue. Reset first, as virtinput_freeze() already does. With the preceding core change, reset waits for callbacks before input_unregister_device() can free vi->idev. Recheck vi->ready after taking the lock again: keep draining completed events so an input packet is not truncated, but stop requeueing buffers and kicking the queue. With evdev attached, input_unregister_handle() currently waits for an RCU grace period, which also waits out IRQ callbacks. This masks the lifetime bug on PCI and MMIO, but does not protect sleepable callbacks on other transports.

Affected

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

271c865161c57cfabca45b93eaa712b19da365bc4.1
Vendor states this is fixed in 3ae729b1f8ab81d1244061872db2fb0ebb110d2a (fixed)
Vendor states this is fixed in 5378f7945856a5ed88e6f9850bc7a68f54090135 (fixed)
Vendor states this is fixed in 81073bca2062c916c818f2744fbab545a5c4982b (fixed)
Vendor states this is fixed in 8226aeee9b9a94cd699fbb51cb230feff46cfaf2 (fixed)
Vendor states this is fixed in a3ba86a270dd87460759214046dc7cbd409ac711 (fixed)
Vendor states this is fixed in d7808b37da0a619cf1fa541c2384e783fecc2480 (fixed)
Vendor states this is fixed in 4.1 (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