vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 7f2d6b31089e48db4653df832c9a6afdde9a1c29, 8e872c07e40d51a66dee7b280a23a460a2e1e3fa, a26b499b757cfc8bbff1088bb1b844639e250893; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
Low priority for now. Upgrade to Linux Linux 7f2d6b31089e48db4653df832c9a6afdde9a1c29, 8e872c07e40d51a66dee7b280a23a460a2e1e3fa, a26b499b757cfc8bbff1088bb1b844639e250893; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.2affected
- 4db52602a6074e9cc523500b8304600ff63e7b85 and later · before 8e872c07e40d51a66dee7b280a23a460a2e1e3faaffected · git
- 4db52602a6074e9cc523500b8304600ff63e7b85 and later · before ed7d5599e6c398da74845767cd1e6a8370a160fcaffected · git
- 4db52602a6074e9cc523500b8304600ff63e7b85 and later · before 7f2d6b31089e48db4653df832c9a6afdde9a1c29affected · git
- 4db52602a6074e9cc523500b8304600ff63e7b85 and later · before a3a8afa2f6e7f0dc266d08f02be3f3054241ba47affected · git
- 4db52602a6074e9cc523500b8304600ff63e7b85 and later · before a26b499b757cfc8bbff1088bb1b844639e250893affected · git
- before 6.2not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
- 6.12.96 and later · up to and including 6.12.*not affected · semver
- 6.18.39 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64472Jul 25, 2026 · vfio/mlx5: Fix racy bitfields and tighten struct layout0Monitor
- ← EarlierCVE-2026-64473Jul 25, 2026 · vfio: Remove device debugfs before releasing devres0Monitor
- Later →CVE-2026-64476Jul 25, 2026 · vfio/pci: Latch disable_idle_d3 per device0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 7f2d6b31089e48db4653df832c9a6afdde9a1c29 | Vendor (CNA) |
| Linux Linux | 8e872c07e40d51a66dee7b280a23a460a2e1e3fa | Vendor (CNA) |
| Linux Linux | a26b499b757cfc8bbff1088bb1b844639e250893 | Vendor (CNA) |
| Linux Linux | a3a8afa2f6e7f0dc266d08f02be3f3054241ba47 | Vendor (CNA) |
| Linux Linux | ed7d5599e6c398da74845767cd1e6a8370a160fc | Vendor (CNA) |
| azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 | 6.6.145.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.96-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.