CVE-2026-99722
What it is
In the Linux kernel, the following vulnerability has been resolved: vringh: bound top-level re-entry into indirect tables In __vringh_iov(), the F_INDIRECT 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 indirect_count 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 __vringh_iov(), 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 indirect_count still bounds a single table, so legitimate chains (including the multiple-indirect case in tools/virtio/vringh_test.c) stay within vring.num, while a cyclic indirect descriptor is now rejected with -ELOOP.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 8d8fae59c6b00cb6b2d48e1496b8a4cc2f4d5e8f
- Linux < e7d831fd55e61f76d5dafe4b5e53aa9c87f7c227
- Linux < f6b933a9a1ebf67ae5474bfb8824500457dfbb68
- Linux < f898439ace7f89922e853b43bcbfcd26ea2e0a98
- Linux 45984b3ae9d688a913d024551848d068b1c0ac4e
- Linux 29c3f932b422d92115e260a250fd910d46cd0c09
- Linux 4511b505057b86a5e898b7244c715422ce59864f
- Linux 1a36f77dc23c3768e06cdc32777b2d85be7f4150
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99722.md and follow it. Check whether this project is affected by CVE-2026-99722. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.