Answer in brief
CVE-2026-80676 records a Unknown severity vulnerability in Drivers: hv: vmbus: use generic driver_override infrastructure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d765edbb301c0e196015a59b17420558088ea33f <d1cb12ae81d2f7a58b0b1cfb51862afca98e6058 || >=d765edbb301c0e196015a59b17420558088ea33f <0e2f0833556c8c5269deb457b89d538644a3b747 || >=d765edbb301c0e196015a59b17420558088ea33f <2fb010ea7ca98cd09a6d365260b769f627e73a76 || >=d765edbb301c0e196015a59b17420558088ea33f <331d8900121a1d74ecd45cd2db742ddcb5a0a565 | d1cb12ae81d2f7a58b0b1cfb51862afca98e6058, 0e2f0833556c8c5269deb457b89d538644a3b747, 2fb010ea7ca98cd09a6d365260b769f627e73a76, 331d8900121a1d74ecd45cd2db742ddcb5a0a565 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
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]
Quoted source text, attributed separately from HOL analysis.