Linux Kernel up to 6.6.144/6.12.95/6.18.38/7.1.3 Vfio vfio_mig_get_next_state infinite loop

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.
3.3$0-$5k0.80

Summaryinfo

A vulnerability categorized as problematic has been discovered in Linux Kernel up to 6.6.144/6.12.95/6.18.38/7.1.3. Affected is the function vfio_mig_get_next_state of the component Vfio. Executing a manipulation can lead to infinite loop. This vulnerability is tracked as CVE-2026-64474. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.144/6.12.95/6.18.38/7.1.3. It has been declared as problematic. This vulnerability affects the function vfio_mig_get_next_state of the component Vfio. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc vfio_mig_get_next_state() walks vfio_from_fsm_table[] one step at a time, looping to skip optional states the device does not support until *next_fsm is supported. A blocked transition is encoded as VFIO_DEVICE_STATE_ERROR, which the trailing return reports as -EINVAL. The skip loop does not account for the ERROR sentinel. state_flags_table[ERROR] is ~0U and vfio_from_fsm_table[ERROR][*] is ERROR, so once *next_fsm becomes ERROR the loop condition stays true and *next_fsm never changes. The blocked arcs STOP_COPY -> PRE_COPY and STOP_COPY -> PRE_COPY_P2P map to ERROR yet pass the support check on a precopy-capable device, causing the loop to spin forever while holding the driver state mutex. This can result in a soft lockup, and a panic with softlockup_panic set. Terminate the skip loop on the ERROR sentinel so a blocked transition falls through to the existing return and reports -EINVAL.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-64474 since 07/19/2026. The exploitation appears to be easy. The attack needs to be approached locally. Additional levels of successful authentication are required for exploitation. There are known technical details, but no exploit is available.

Upgrading to version 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch 8e872c07e40d51a66dee7b280a23a460a2e1e3fa/ed7d5599e6c398da74845767cd1e6a8370a160fc/7f2d6b31089e48db4653df832c9a6afdde9a1c29/a3a8afa2f6e7f0dc266d08f02be3f3054241ba47/a26b499b757cfc8bbff1088bb1b844639e250893 is able to eliminate this problem.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.4
VulDB Meta Temp Score: 3.3

VulDB Base Score: 3.4
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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 6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc1
Patch: 8e872c07e40d51a66dee7b280a23a460a2e1e3fa/ed7d5599e6c398da74845767cd1e6a8370a160fc/7f2d6b31089e48db4653df832c9a6afdde9a1c29/a3a8afa2f6e7f0dc266d08f02be3f3054241ba47/a26b499b757cfc8bbff1088bb1b844639e250893

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-64474 (🔒)
GCVE (CVE): GCVE-0-2026-64474
GCVE (VulDB): GCVE-100-383272

Entryinfo

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

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!