Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97986virtio_input: stop callbacks before unregistering input device

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < 3ae729b1f8ab81d1244061872db2fb0ebb110d2a
    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < 81073bca2062c916c818f2744fbab545a5c4982b
    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < 8226aeee9b9a94cd699fbb51cb230feff46cfaf2
    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < a3ba86a270dd87460759214046dc7cbd409ac711
    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < 5378f7945856a5ed88e6f9850bc7a68f54090135
    • affected 271c865161c57cfabca45b93eaa712b19da365bc – < d7808b37da0a619cf1fa541c2384e783fecc2480
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97986 badge
[![CVE-2026-97986](https://cveledger.app/badge/CVE-2026-97986.svg)](https://cveledger.app/cve/CVE-2026-97986)

Record last updated .