Linux Kernel up to 7.2-rc1 Vfio Pci vfio_pci_core_register_device 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.
8.7$5k-$25k2.39

Summaryinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 7.2-rc1. Affected by this issue is the function vfio_pci_core_register_device of the component Vfio Pci. This manipulation causes use after free. This vulnerability appears as CVE-2026-64475. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2-rc1. It has been declared as very critical. Affected by this vulnerability is the function vfio_pci_core_register_device of the component Vfio Pci. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration. In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device. Add the required VGA unwind callout.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-64475 since 07/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. 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 07/25/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc2 eliminates this vulnerability. Applying the patch 0f2a35a0c7ea7da347b814750eaa78adf3582381/8d65decde9afd2bd78bcfffdc0df73b82a0b5509/ef4c38d30b3744e89eb5048218904bb629ea8d47/9e0a3f642e607848669235f5069f35640abbfc88/42d758a09d2c46c42357ecde9a5492f015bde2e5/52adb2dff7ce3d8430e2bdc5988b618a430def85/278a5659c391fe5afe5f9ce1bad1fd24e90144f1/daedde7f024ecf88bc8e832ed40cf2c795f0796a is able to eliminate this problem.

Be aware that VulDB is the high quality source 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.1
VulDB Meta Temp Score: 8.7

VulDB Base Score: 9.1
VulDB Temp Score: 8.7
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

EPSS Score: 🔒
EPSS Percentile: 🔒

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 5.10.261/5.15.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc2
Patch: 0f2a35a0c7ea7da347b814750eaa78adf3582381/8d65decde9afd2bd78bcfffdc0df73b82a0b5509/ef4c38d30b3744e89eb5048218904bb629ea8d47/9e0a3f642e607848669235f5069f35640abbfc88/42d758a09d2c46c42357ecde9a5492f015bde2e5/52adb2dff7ce3d8430e2bdc5988b618a430def85/278a5659c391fe5afe5f9ce1bad1fd24e90144f1/daedde7f024ecf88bc8e832ed40cf2c795f0796a

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64475 (🔒)
GCVE (CVE): GCVE-0-2026-64475
GCVE (VulDB): GCVE-100-383263

Entryinfo

Created: 07/25/2026 19:01
Changes: 07/25/2026 19:01 (59)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!