Answer in brief
CVE-2026-64475 records a Unknown severity vulnerability in vfio/pci: Release the VGA arbiter client on register_device() failure. 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.
Answer in brief
CVE-2026-64475 records a Unknown severity vulnerability in vfio/pci: Release the VGA arbiter client on register_device() failure. 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 | >=87856f9af04eaacf9848710625a4ffee1d020fa9 <0f2a35a0c7ea7da347b814750eaa78adf3582381 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <8d65decde9afd2bd78bcfffdc0df73b82a0b5509 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <ef4c38d30b3744e89eb5048218904bb629ea8d47 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <9e0a3f642e607848669235f5069f35640abbfc88 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <42d758a09d2c46c42357ecde9a5492f015bde2e5 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <52adb2dff7ce3d8430e2bdc5988b618a430def85 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <278a5659c391fe5afe5f9ce1bad1fd24e90144f1 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <daedde7f024ecf88bc8e832ed40cf2c795f0796a || d62dccb417cf972c978bf3c68a7d5e846bcf953e || 6694b8daffac5a8661071f085608afc78f7acd08 || >=5.10.37 <5.10.261 || >=5.11.21 <5.12 || >=5.12.4 <5.13 | 0f2a35a0c7ea7da347b814750eaa78adf3582381, 8d65decde9afd2bd78bcfffdc0df73b82a0b5509, ef4c38d30b3744e89eb5048218904bb629ea8d47, 9e0a3f642e607848669235f5069f35640abbfc88, 42d758a09d2c46c42357ecde9a5492f015bde2e5, 52adb2dff7ce3d8430e2bdc5988b618a430def85, 278a5659c391fe5afe5f9ce1bad1fd24e90144f1, daedde7f024ecf88bc8e832ed40cf2c795f0796a, 5.10.261, 5.12, 5.13 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration. In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device. Add the required VGA unwind callout.
Quoted source text, attributed separately from HOL analysis.
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 | >=87856f9af04eaacf9848710625a4ffee1d020fa9 <0f2a35a0c7ea7da347b814750eaa78adf3582381 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <8d65decde9afd2bd78bcfffdc0df73b82a0b5509 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <ef4c38d30b3744e89eb5048218904bb629ea8d47 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <9e0a3f642e607848669235f5069f35640abbfc88 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <42d758a09d2c46c42357ecde9a5492f015bde2e5 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <52adb2dff7ce3d8430e2bdc5988b618a430def85 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <278a5659c391fe5afe5f9ce1bad1fd24e90144f1 || >=4aeec3984ddc853f7c65903bde472ffdef738bae <daedde7f024ecf88bc8e832ed40cf2c795f0796a || d62dccb417cf972c978bf3c68a7d5e846bcf953e || 6694b8daffac5a8661071f085608afc78f7acd08 || >=5.10.37 <5.10.261 || >=5.11.21 <5.12 || >=5.12.4 <5.13 | 0f2a35a0c7ea7da347b814750eaa78adf3582381, 8d65decde9afd2bd78bcfffdc0df73b82a0b5509, ef4c38d30b3744e89eb5048218904bb629ea8d47, 9e0a3f642e607848669235f5069f35640abbfc88, 42d758a09d2c46c42357ecde9a5492f015bde2e5, 52adb2dff7ce3d8430e2bdc5988b618a430def85, 278a5659c391fe5afe5f9ce1bad1fd24e90144f1, daedde7f024ecf88bc8e832ed40cf2c795f0796a, 5.10.261, 5.12, 5.13 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration. In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device. Add the required VGA unwind callout.
Quoted source text, attributed separately from HOL analysis.