CVE-2026-80676: Linux kernel · Drivers: hv: vmbus: use generic driver_override infrastructure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d1cb12ae81d2f7a58b0b1cfb51862afca98e6058 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d1cb12ae81d2f7a58b0b1cfb51862afca98e6058, a1656234a4a2dc6e975546867887c5f63e4a90f0, 331d8900121a1d74ecd45cd2db742ddcb5a0a565 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
References
- git.kernel.org/stable/c/a1656234a4a2dc6e975546867887c5f63e4a90f0 (opens in a new tab)
- git.kernel.org/stable/c/d1cb12ae81d2f7a58b0b1cfb51862afca98e6058 (opens in a new tab)
- git.kernel.org/stable/c/0e2f0833556c8c5269deb457b89d538644a3b747 (opens in a new tab)
- git.kernel.org/stable/c/2fb010ea7ca98cd09a6d365260b769f627e73a76 (opens in a new tab)
- git.kernel.org/stable/c/331d8900121a1d74ecd45cd2db742ddcb5a0a565 (opens in a new tab)