CVE-2026-64473: Linux kernel · vfio: Remove device debugfs before releasing devres VFIO device debugfs files created
Affects Linux kernelSource GCVE Database
Not known to be exploited · fixed in 6.8.0-147.147 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 06:59 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-147.147, 6.8.0-1067.70, 7.0.0-1012.12~24.04.1 +28
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8917-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and included in Linux kernel versions 6.8.0-147.147, 6.8.0-1067.70, 7.0.0-1012.12~24.04.1, and other related releases. Users should update to these fixed kernel versions to remediate the vulnerability. No additional mitigation actions are required as the fix addresses the root cause by correcting the debugfs cleanup sequence.
Description
A vulnerability in the Linux kernel's VFIO subsystem was fixed by changing the order of debugfs cleanup during device unregister. The issue involved debugfs entries retaining stale inode private data after device resources were released, potentially causing confusion during device unregister. The fix removes the per-device debugfs tree before device deletion and clears the debugfs root to prevent stale entries from being mistaken as live. This vulnerability affects multiple Linux kernel versions prior to fixed releases in the 6.8 and 7.0 series.
References
- ubuntu.com/security/CVE-2026-64473 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-64473 (opens in a new tab)
- git.kernel.org/linus/dc7fe87de492ea7f33a72b78d26650b75bf37f4f (opens in a new tab)
- git.kernel.org/stable/c/6cc60b41d61657dc469893d14e8e55d160056ff1 (opens in a new tab)
- git.kernel.org/stable/c/a53109ffb6b5148e11a27fb7670355b92db12dd3 (opens in a new tab)
- git.kernel.org/stable/c/a5df401dc84f091e20b045560569f0736758fea7 (opens in a new tab)
- git.kernel.org/stable/c/dc7fe87de492ea7f33a72b78d26650b75bf37f4f (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8917-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8918-1 (opens in a new tab)