vhost: fix used ring index wrap in vhost_add_used_n_in_order
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0, Kernel e244725e86be02cd85cb878b3ed8570eba2e4be1, Kernel ebdc350cfb1740b6411420482e58a35cc4761628 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: vhost: fix used ring index wrap in vhost_add_used_n_in_order vhost_add_used_n_in_order() advances start by nheads[i] but wraps it with a single subtraction. If start + nheads[i] >= 2 * vq->num, start can remain outside the ring. With used-ring logging enabled, start > vq->num makes (vq->num - start) underflow. log_write() then sets bits beyond the dirty-log bitmap, potentially corrupting adjacent userspace memory. This is reachable on the vhost-net TX path with VIRTIO_F_IN_ORDER: done_idx can reach VHOST_NET_BATCH (64), triggering the issue with a 32-entry ring. Wrap start with a mask to keep it within the ring. VHOST_SET_VRING_NUM enforces a nonzero power-of-two ring size, allowing start to be wrapped using & (vq->num - 1).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=67a873df0c410915275f735fedb401b9637d6faf <308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0, >=67a873df0c410915275f735fedb401b9637d6faf <e244725e86be02cd85cb878b3ed8570eba2e4be1, >=67a873df0c410915275f735fedb401b9637d6faf <ebdc350cfb1740b6411420482e58a35cc4761628 | 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0, e244725e86be02cd85cb878b3ed8570eba2e4be1, ebdc350cfb1740b6411420482e58a35cc4761628 |
| linux-kernel: Kernel | >=6.17.0 <6.18.64, >=6.19.0 <7.3.5 | 6.18.64, 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket