In the Linux kernel, the following vulnerability has been resolved: vfio: Remove device debugfs before releasing devres VFIO device debugfs files… (CVE-2026-64473)
A vulnerability in the Linux kernel's VFIO subsystem related to debugfs handling has been resolved. The issue involved debugfs entries retaining stale inode private data after device removal, due to improper ordering of resource release calls. This could cause debugfs entries to remain visible with invalid backing storage during device unregistering. The fix removes the per-device debugfs tree before releasing device resources and clears the debugfs root after removal to prevent confusion with live debugfs entries.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel VFIO subsystem arises because debugfs files created with debugfs_create_devm_seqfile() store devres-allocated data as inode private data. The unregister sequence called vfio_device_del() before vfio_device_debugfs_exit(), but vfio_device_del() releases devres, leaving debugfs entries visible with stale inode data while unregister waits for userspace references to drain. The fix changes the sequence to remove the per-device debugfs tree before calling vfio_device_del(), and clears the debugfs root after removal, preventing stale debugfs entries from being visible during device unregister.
Potential Impact
The impact is limited to diagnostic debugfs entries potentially exposing stale inode private data during device unregister. This could cause confusion or misinterpretation of debug information but does not directly indicate a security compromise or system stability issue. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to remove the per-device debugfs tree before releasing device resources and to clear the debugfs root after removal. Users should apply the updated Linux kernel version containing this fix. No additional mitigation actions are indicated.
In the Linux kernel, the following vulnerability has been resolved: vfio: Remove device debugfs before releasing devres VFIO device debugfs files… (CVE-2026-64473)
Description
A vulnerability in the Linux kernel's VFIO subsystem related to debugfs handling has been resolved. The issue involved debugfs entries retaining stale inode private data after device removal, due to improper ordering of resource release calls. This could cause debugfs entries to remain visible with invalid backing storage during device unregistering. The fix removes the per-device debugfs tree before releasing device resources and clears the debugfs root after removal to prevent confusion with live debugfs entries.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel VFIO subsystem arises because debugfs files created with debugfs_create_devm_seqfile() store devres-allocated data as inode private data. The unregister sequence called vfio_device_del() before vfio_device_debugfs_exit(), but vfio_device_del() releases devres, leaving debugfs entries visible with stale inode data while unregister waits for userspace references to drain. The fix changes the sequence to remove the per-device debugfs tree before calling vfio_device_del(), and clears the debugfs root after removal, preventing stale debugfs entries from being visible during device unregister.
Potential Impact
The impact is limited to diagnostic debugfs entries potentially exposing stale inode private data during device unregister. This could cause confusion or misinterpretation of debug information but does not directly indicate a security compromise or system stability issue. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to remove the per-device debugfs tree before releasing device resources and to clear the debugfs root after removal. Users should apply the updated Linux kernel version containing this fix. No additional mitigation actions are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fm4h-cjxv-2ppf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64473"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542069c2644c7f80823d0
Added to database: 07/25/2026, 23:08:54 UTC
Last enriched: 07/25/2026, 23:17:07 UTC
Last updated: 07/26/2026, 06:18:03 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.