Menu

Star on GitHub · 3.2k

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' matc…

Published Aug 28, 2026EPSS 0.21%

Overview

CVE-2026-80676 is a known-severity vulnerability. It was published on August 28, 2026.

Technical 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]

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80676?

CVE-2026-80676 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-80676?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80676?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80676?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80676 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.