CVE-2026-97986: virtio_input: stop callbacks before unregistering input device
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 3ae729b1f8ab81d1244061872db2fb0ebb110d2a, 5378f7945856a5ed88e6f9850bc7a68f54090135, 81073bca2062c916c818f2744fbab545a5c4982b; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3ae729b1f8ab81d1244061872db2fb0ebb110d2a, 5378f7945856a5ed88e6f9850bc7a68f54090135, 81073bca2062c916c818f2744fbab545a5c4982b; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.1affected
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before 3ae729b1f8ab81d1244061872db2fb0ebb110d2aaffected · git
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before 81073bca2062c916c818f2744fbab545a5c4982baffected · git
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before 8226aeee9b9a94cd699fbb51cb230feff46cfaf2affected · git
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before a3ba86a270dd87460759214046dc7cbd409ac711affected · git
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before 5378f7945856a5ed88e6f9850bc7a68f54090135affected · git
- 271c865161c57cfabca45b93eaa712b19da365bc and later · before d7808b37da0a619cf1fa541c2384e783fecc2480affected · git
- before 4.1not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97984Sep 25, 2026 · net: ipv6: Fix UDP length overflow with PMTU discover and big MTU0Monitor
- ← EarlierCVE-2026-97985Sep 25, 2026 · af_unix: Update last skb marker in manage_oob().0Monitor
- Later →CVE-2026-97987Sep 25, 2026 · virtio_input: reset device if input_register_device() fails0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3ae729b1f8ab81d1244061872db2fb0ebb110d2a | Vendor (CNA) |
| Linux Linux | 5378f7945856a5ed88e6f9850bc7a68f54090135 | Vendor (CNA) |
| Linux Linux | 81073bca2062c916c818f2744fbab545a5c4982b | Vendor (CNA) |
| Linux Linux | 8226aeee9b9a94cd699fbb51cb230feff46cfaf2 | Vendor (CNA) |
| Linux Linux | a3ba86a270dd87460759214046dc7cbd409ac711 | Vendor (CNA) |
| Linux Linux | d7808b37da0a619cf1fa541c2384e783fecc2480 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5378f7945856a5ed88e6f9850bc7a68f54090135
- git.kernel.org/stable/c/81073bca2062c916c818f2744fbab545a5c4982b
- git.kernel.org/stable/c/8226aeee9b9a94cd699fbb51cb230feff46cfaf2
- git.kernel.org/stable/c/a3ba86a270dd87460759214046dc7cbd409ac711
- git.kernel.org/stable/c/d7808b37da0a619cf1fa541c2384e783fecc2480
Vendor advisories and official records. Exploit/PoC links are deliberately left out.