xen-netback: reject zero-queue configuration from guest
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8d3d53b3e43363e79ab9a9ecc149b06c1314b25d · < 654780dee9eae419e1648ea58462c4efe54518fa| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xen-netback: reject zero-queue configuration from guest
A malicious or buggy Xen guest can write "0" to the xenbus key "multi-queue-num-queues". The connect() function in the backend only validates the upper bound (requested_num_queues > xenvif_max_queues) but not zero, allowing requested_num_queues=0 to reach vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers WARN_ON_ONCE(!size) in __vmalloc_node_range().
On systems with panic_on_warn=1, this allows a guest-to-host denial of service.
The Xen network interface specification requires the queue count to be "greater than zero".
Add a zero check to match the validation already present in xen-blkback, which has included this guard since its multi-queue support was added.
From the CVE record · Linux
The Linux kernel’s xen-netback component accepts a zero-queue configuration from a Xen guest, triggering a kernel warning. A malicious or buggy guest can cause a host denial of service when the host has panic_on_warn=1; this requires access as a Xen guest, not host authentication or user interaction.
Operators of Linux hosts using Xen network backends should check their kernel versions against the vendor advisory; affected versions were not provided.