← Back to the live CVE advisory feed

CVE-2026-80693: Linux

Severity

9.3 (CRITICAL)

Vendor

LINUX

Affected versions

d4d5587182664b0c4ab6d3556ce881cb975507c2 through before 41bb8748124d0d8ee5d8e1eace9dfbc874bc9564; d4d5587182664b0c4ab6d3

Patch status

Patched

Published

2026-08-28T08:16:54.787

Modified

2026-08-29T07:16:51.463

Why it matters

Critical vulnerability requiring immediate validation against your environment.

Recommended admin actions

• Prioritize validation immediately due to critical CVSS severity.

Technical summary

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.

View the official NVD record for CVE-2026-80693

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.