CVE-2026-99722: vringh: bound top-level re-entry into indirect tables
In the Linux kernel, the following vulnerability has been resolved:
vringh: bound top-level re-entry into indirect tables
In vringhiov(), the FINDIRECT branch descends into the indirect table and continues before the descriptor accounting runs. A top-level indirect descriptor is therefore never charged to count. If such a descriptor sets NEXT to point back at itself, returning from the indirect table resumes at the same top-level descriptor, which is again not counted, so the walk never makes forward progress.
Because count stays flat and indirectcount is reset to 0 on every return to the top-level table, neither bound in the loop check trips. A guest can spin the vringh worker at 100% CPU inside vringhiov(), an uninterruptible host DoS.
Move the descriptor accounting above the indirect switch so that a top-level indirect descriptor is charged one top-level traversal step before the walk descends into its table, bringing this re-entry under the existing vrh->vring.num bound. Each top-level descriptor is still charged at most one step and indirectcount still bounds a single table, so legitimate chains (including the multiple-indirect case in tools/virtio/vringhtest.c) stay within vring.num, while a cyclic indirect descriptor is now rejected with -ELOOP.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.10 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.15 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.20 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.5 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.11 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.16 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.18 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.19 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Hosts that process guest-provided virtio descriptor chains through the vringh worker are exposed. The vulnerable path is in __vringh_iov().
What does an attacker need to trigger the denial of service?
A guest needs to provide a top-level indirect descriptor whose NEXT field points back to that same descriptor. Re-entering the top-level descriptor avoids the prior accounting bounds and prevents the walk from making forward progress.
What is the practical impact of successful exploitation?
The vringh worker can spin at 100% CPU in __vringh_iov(), causing an uninterruptible host denial of service.
How can an affected system be identified during an incident?
A likely symptom is a vringh worker consuming 100% CPU while executing in __vringh_iov(). The triggering descriptor pattern is a top-level indirect descriptor with NEXT referring to itself.