CVE-2026-64473
Last modified
CVE-2026-64473 is a vulnerability of currently unknown severity. 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().
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 2202844e4468c7539dba0c0b06577c93735af952, < 6cc60b41d61657dc469893d14e8e55d160056ff1; >= 2202844e4468c7539dba0c0b06577c93735af952, < a53109ffb6b5148e11a27fb7670355b92db12dd3; >= 2202844e4468c7539dba0c0b06577c93735af952, < a5df401dc84f091e20b045560569f0736758fea7; >= 2202844e4468c7539dba0c0b06577c93735af952, < dc7fe87de492ea7f33a72b78d26650b75bf37f4f |
| Linux | Linux | 6.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-64473?
How severe is CVE-2026-64473?
How do I fix CVE-2026-64473?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64468In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64469In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6447The Call for Price for WooCommerce plugin for WordPress is v…4.4
- CVE-2026-64470In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64471In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64472In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64474In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64475In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64476In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64477In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64478In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64479In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-64473?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
