Answer in brief
CVE-2026-64474 records a Unknown severity vulnerability in vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4db52602a6074e9cc523500b8304600ff63e7b85 <8e872c07e40d51a66dee7b280a23a460a2e1e3fa || >=4db52602a6074e9cc523500b8304600ff63e7b85 <ed7d5599e6c398da74845767cd1e6a8370a160fc || >=4db52602a6074e9cc523500b8304600ff63e7b85 <7f2d6b31089e48db4653df832c9a6afdde9a1c29 || >=4db52602a6074e9cc523500b8304600ff63e7b85 <a3a8afa2f6e7f0dc266d08f02be3f3054241ba47 || >=4db52602a6074e9cc523500b8304600ff63e7b85 <a26b499b757cfc8bbff1088bb1b844639e250893 | 8e872c07e40d51a66dee7b280a23a460a2e1e3fa, ed7d5599e6c398da74845767cd1e6a8370a160fc, 7f2d6b31089e48db4653df832c9a6afdde9a1c29, a3a8afa2f6e7f0dc266d08f02be3f3054241ba47, a26b499b757cfc8bbff1088bb1b844639e250893 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64474 records a Unknown severity vulnerability in vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4db52602a6074e9cc523500b8304600ff63e7b85 <8e872c07e40d51a66dee7b280a23a460a2e1e3fa || >=4db52602a6074e9cc523500b8304600ff63e7b85 <ed7d5599e6c398da74845767cd1e6a8370a160fc || >=4db52602a6074e9cc523500b8304600ff63e7b85 <7f2d6b31089e48db4653df832c9a6afdde9a1c29 || >=4db52602a6074e9cc523500b8304600ff63e7b85 <a3a8afa2f6e7f0dc266d08f02be3f3054241ba47 || >=4db52602a6074e9cc523500b8304600ff63e7b85 <a26b499b757cfc8bbff1088bb1b844639e250893 | 8e872c07e40d51a66dee7b280a23a460a2e1e3fa, ed7d5599e6c398da74845767cd1e6a8370a160fc, 7f2d6b31089e48db4653df832c9a6afdde9a1c29, a3a8afa2f6e7f0dc266d08f02be3f3054241ba47, a26b499b757cfc8bbff1088bb1b844639e250893 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.