CVE-2026-64473: vfio: Remove device debugfs before releasing devres
In the Linux kernel, the following vulnerability has been resolved:
vfio: Remove device debugfs before releasing devres
VFIO device debugfs files created with debugfscreatedevmseqfile() store a devres allocated debugfsdevmentry as inode private data. vfiounregistergroupdev() currently calls vfiodevicedel() before vfiodevicedebugfsexit(), but devicedel() releases devres. This can leave debugfs entries visible with stale inode private data while unregister waits for userspace references to drain.
Remove the per-device debugfs tree before vfiodevicedel(). The debugfs view is diagnostic only, so losing it at the start of unregister is preferable to preserving entries whose backing storage may already have been released.
Complete the teardown by clearing the per-device debugfs root after removal. This matches the global debugfs root cleanup and prevents future users from mistaking a removed dentry for a live debugfs tree during the remainder of unregister.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64473?
CVE-2026-64473 has a risk level of 12, indicating a critical vulnerability.
How do I fix CVE-2026-64473?
To fix CVE-2026-64473, update your Linux kernel to the latest version where the vulnerability has been resolved.
What is CVE-2026-64473 about?
CVE-2026-64473 involves the unsafe handling of vfio device debugfs files in the Linux kernel, leading to potential security issues.
Which versions of the Linux kernel are affected by CVE-2026-64473?
CVE-2026-64473 affects certain versions of the Linux kernel prior to the fix provided in the latest updates.
What are the potential impacts of CVE-2026-64473?
Exploitation of CVE-2026-64473 could result in unauthorized access or manipulation of vfio device debugfs files.