Linux Kernel up to 6.12.96/6.18.39/7.1.4 vmbus __driver_attach use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.73

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.96/6.18.39/7.1.4. It has been rated as very critical. Affected by this vulnerability is the function __driver_attach of the component vmbus. Performing a manipulation results in use after free. This vulnerability is reported as CVE-2026-80676. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.96/6.18.39/7.1.4. It has been classified as very critical. This affects the function __driver_attach of the component vmbus. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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]

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80676 since 08/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/28/2026).

Upgrading to version 6.12.97, 6.18.40 or 7.1.5 eliminates this vulnerability. Applying the patch d1cb12ae81d2f7a58b0b1cfb51862afca98e6058/0e2f0833556c8c5269deb457b89d538644a3b747/2fb010ea7ca98cd09a6d365260b769f627e73a76/331d8900121a1d74ecd45cd2db742ddcb5a0a565 is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.97/6.18.40/7.1.5
Patch: d1cb12ae81d2f7a58b0b1cfb51862afca98e6058/0e2f0833556c8c5269deb457b89d538644a3b747/2fb010ea7ca98cd09a6d365260b769f627e73a76/331d8900121a1d74ecd45cd2db742ddcb5a0a565

Timelineinfo

08/26/2026 CVE reserved
08/28/2026 +2 days Advisory disclosed
08/28/2026 +0 days VulDB entry created
08/28/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80676 (🔒)
GCVE (CVE): GCVE-0-2026-80676
GCVE (VulDB): GCVE-100-396627

Entryinfo

Created: 08/28/2026 10:55
Changes: 08/28/2026 10:55 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!