Answer in brief
CVE-2026-64473 records a Unknown severity vulnerability in vfio: Remove device debugfs before releasing devres. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2202844e4468c7539dba0c0b06577c93735af952 <6cc60b41d61657dc469893d14e8e55d160056ff1 || >=2202844e4468c7539dba0c0b06577c93735af952 <a53109ffb6b5148e11a27fb7670355b92db12dd3 || >=2202844e4468c7539dba0c0b06577c93735af952 <a5df401dc84f091e20b045560569f0736758fea7 || >=2202844e4468c7539dba0c0b06577c93735af952 <dc7fe87de492ea7f33a72b78d26650b75bf37f4f | 6cc60b41d61657dc469893d14e8e55d160056ff1, a53109ffb6b5148e11a27fb7670355b92db12dd3, a5df401dc84f091e20b045560569f0736758fea7, dc7fe87de492ea7f33a72b78d26650b75bf37f4f |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64473 records a Unknown severity vulnerability in vfio: Remove device debugfs before releasing devres. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2202844e4468c7539dba0c0b06577c93735af952 <6cc60b41d61657dc469893d14e8e55d160056ff1 || >=2202844e4468c7539dba0c0b06577c93735af952 <a53109ffb6b5148e11a27fb7670355b92db12dd3 || >=2202844e4468c7539dba0c0b06577c93735af952 <a5df401dc84f091e20b045560569f0736758fea7 || >=2202844e4468c7539dba0c0b06577c93735af952 <dc7fe87de492ea7f33a72b78d26650b75bf37f4f | 6cc60b41d61657dc469893d14e8e55d160056ff1, a53109ffb6b5148e11a27fb7670355b92db12dd3, a5df401dc84f091e20b045560569f0736758fea7, dc7fe87de492ea7f33a72b78d26650b75bf37f4f |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.