CVE-2026-80676

Unknown

Last modified

CVE-2026-80676 is a vulnerability of currently unknown severity. 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].

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]

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= d765edbb301c0e196015a59b17420558088ea33f, < d1cb12ae81d2f7a58b0b1cfb51862afca98e6058; >= d765edbb301c0e196015a59b17420558088ea33f, < 0e2f0833556c8c5269deb457b89d538644a3b747; >= d765edbb301c0e196015a59b17420558088ea33f, < 2fb010ea7ca98cd09a6d365260b769f627e73a76; >= d765edbb301c0e196015a59b17420558088ea33f, < 331d8900121a1d74ecd45cd2db742ddcb5a0a565
LinuxLinux4.20

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80676?
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]
How severe is CVE-2026-80676?
Severity scoring for CVE-2026-80676 is pending analysis.
How do I fix CVE-2026-80676?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80676?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST