CVE-2026-99722: vringh: bound top-level re-entry into indirect tables

Published Nov 20, 2026
·
Updated

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

15 affected componentsFixes available
linux/kernel>=4.9.318<4.10
4.10
linux/kernel>=4.14.283<4.15
4.15
linux/kernel>=4.19.247<4.20
4.20
linux/kernel>=5.4.198<5.5
5.5
linux/kernel>=5.10.122<5.11
5.11
linux/kernel>=5.15.47<5.16
5.16
linux/kernel>=5.17.15<5.18
5.18
linux/kernel>=5.18.4<5.19
5.19
linux/kernel>=5.19.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 4.10
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 4.15
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 4.20
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.5
  5. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.11
  6. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.16
  7. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.18
  8. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.19
  9. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  10. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  11. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  12. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

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().

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203