CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0f2a35a0c7ea7da347b814750eaa78adf3582381, 278a5659c391fe5afe5f9ce1bad1fd24e90144f1, 42d758a09d2c46c42357ecde9a5492f015bde2e5; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
Low priority for now. Upgrade to Linux Linux 0f2a35a0c7ea7da347b814750eaa78adf3582381, 278a5659c391fe5afe5f9ce1bad1fd24e90144f1, 42d758a09d2c46c42357ecde9a5492f015bde2e5; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-416
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- d62dccb417cf972c978bf3c68a7d5e846bcf953e, 6694b8daffac5a8661071f085608afc78f7acd08, 5.13affected
- 87856f9af04eaacf9848710625a4ffee1d020fa9 and later · before 0f2a35a0c7ea7da347b814750eaa78adf3582381affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before 8d65decde9afd2bd78bcfffdc0df73b82a0b5509affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before ef4c38d30b3744e89eb5048218904bb629ea8d47affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before 9e0a3f642e607848669235f5069f35640abbfc88affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before 42d758a09d2c46c42357ecde9a5492f015bde2e5affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before 52adb2dff7ce3d8430e2bdc5988b618a430def85affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before 278a5659c391fe5afe5f9ce1bad1fd24e90144f1affected · git
- 4aeec3984ddc853f7c65903bde472ffdef738bae and later · before daedde7f024ecf88bc8e832ed40cf2c795f0796aaffected · git
- 5.10.37 and later · before 5.10.261affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64460Jul 25, 2026 · PCI/IOV: Skip VF Resizable BAR restore on read error28Monitor
- ← EarlierCVE-2026-64463Jul 25, 2026 · usb: typec: tcpci_rt1711h: unregister TCPCI port with devres31Monitor
- Later →CVE-2026-64481Jul 25, 2026 · ALSA: hda/cs35l41: Fix firmware load work teardown31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f2a35a0c7ea7da347b814750eaa78adf3582381 | Vendor (CNA) |
| Linux Linux | 278a5659c391fe5afe5f9ce1bad1fd24e90144f1 | Vendor (CNA) |
| Linux Linux | 42d758a09d2c46c42357ecde9a5492f015bde2e5 | Vendor (CNA) |
| Linux Linux | 5.10.261 | Vendor (CNA) |
| Linux Linux | 5.12 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 52adb2dff7ce3d8430e2bdc5988b618a430def85 | Vendor (CNA) |
| Linux Linux | 8d65decde9afd2bd78bcfffdc0df73b82a0b5509 | Vendor (CNA) |
| Linux Linux | 9e0a3f642e607848669235f5069f35640abbfc88 | Vendor (CNA) |
| Linux Linux | daedde7f024ecf88bc8e832ed40cf2c795f0796a | Vendor (CNA) |
| Linux Linux | ef4c38d30b3744e89eb5048218904bb629ea8d47 | Vendor (CNA) |
| azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 | 6.6.145.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-645230 days apartnet/handshake: Take a long-lived file reference at submit39Monitor
- CVE-2026-645301 days apartnet/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle39Monitor
- CVE-2026-645412 days apartnet/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket39Monitor
- CVE-2026-639226 days apartipv6: exthdrs: refresh nh after handling HAO option39Monitor
- CVE-2026-639796 days apartnet/handshake: hand off the pinned file reference to accept_doit39Monitor
- CVE-2026-6456410 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing39Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/278a5659c391fe5afe5f9ce1bad1fd24e90144f1
- git.kernel.org/stable/c/42d758a09d2c46c42357ecde9a5492f015bde2e5
- git.kernel.org/stable/c/52adb2dff7ce3d8430e2bdc5988b618a430def85
- git.kernel.org/stable/c/8d65decde9afd2bd78bcfffdc0df73b82a0b5509
- git.kernel.org/stable/c/9e0a3f642e607848669235f5069f35640abbfc88
- git.kernel.org/stable/c/daedde7f024ecf88bc8e832ed40cf2c795f0796a
- git.kernel.org/stable/c/ef4c38d30b3744e89eb5048218904bb629ea8d47
Vendor advisories and official records. Exploit/PoC links are deliberately left out.