CVE-2026-99251

Drivers: hv: Avoid infinite retry loop in init_vp_index()

N/A
Published: November 3, 2026 at 11:18 AM UTC
Updated: November 3, 2026 at 12:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A

Description

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: Avoid infinite retry loop in init_vp_index() There is a retry loop in init_vp_index() where the CPUs from a certain node are stripped out if they have already been in the allocated cpumask or not in HK_TYPE_MANAGED_IRQ housekeeping cpumask. If there is no CPU left, the allocated cpumask is ignored and the process is retried again. However, if the HK_TYPE_MANAGED_IRQ housekeeping cpumask turns out not to contain any CPU in that particular node, that will become an infinite retry loop. This particular problem was reported by sashiko [1]. This should rarely happen, but we still need to guard against this. Fix this infinite loop problem by also skipping NUMA node that has no housekeeping CPU in the inner while loop of init_vp_index(). Also update the early abort check to check for the absence of online housekeeping CPUs instead of just the emptiness of the cpumask. As the outer for loop will only be reached if the housekeeping cpumask has at least one online CPU, a NUMA node with housekeeping CPUs will eventually be found.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.196640b5df1a38801be6d0595c8cd2177d968d7ee0
Vendor states this is fixed in 6.1.191 (unaffected)
Vendor states this is fixed in 6.12.115 (unaffected)
Vendor states this is fixed in 6.18.59 (unaffected)
Vendor states this is fixed in 6.6.161 (unaffected)
Vendor states this is fixed in 7.2.13 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card