Strix
74.1K

CVE-2026-99251

Unknown

Last modified

CVE-2026-99251 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < b3993f6dc106ff416c7a613c631e1e0af451aed7; >= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < f561392afb44a8a42c54c1cfd3f33dace0b50537; >= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < 15dd3429f0e76ca071657e480cb7e6ff3a1af730; >= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < 7141331f2d245efc07175802a6bf76badec871ed; >= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < 95fec47cdbf747b81ab22affd7252dda6050ad0c; >= 6640b5df1a38801be6d0595c8cd2177d968d7ee0, < 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd
LinuxLinux5.19

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-99251?
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.
How severe is CVE-2026-99251?
Severity scoring for CVE-2026-99251 is pending analysis.
How do I fix CVE-2026-99251?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-99251?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST