CVE-2026-64473
CVE CVE-2026-64473EUVD EUVD-2026-48817Published 2026-07-25T08:51:36.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: vfio: Remove device debugfs before releasing devres VFIO device debugfs files created with debugfs_create_devm_seqfile() store a devres allocated debugfs_devm_entry as inode private data. vfio_unregister_group_dev() currently calls vfio_device_del() before vfio_device_debugfs_exit(), but device_del() 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 vfio_device_del(). 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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 2202844e4468c7539dba0c0b06577c93735af952 <6cc60b41d61657dc469893d14e8e55d160056ff1; 6.8; patch: 0; patch: 7.2-rc2; patch: 6.12.96; patch: 6.18.39; 2202844e4468c7539dba0c0b06577c93735af952 <dc7fe87de492ea7f33a72b78d26650b75bf37f4f; 2202844e4468c7539dba0c0b06577c93735af952 <a5df401dc84f091e20b045560569f0736758fea7; 2202844e4468c7539dba0c0b06577c93735af952 <a53109ffb6b5148e11a27fb7670355b92db12dd3; patch: 7.1.4
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.