CVE-2026-99251Drivers: hv: Avoid infinite retry loop in init_vp_index()
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 39 days later
· 39 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < b3993f6dc106ff416c7a613c631e1e0af451aed7
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < f561392afb44a8a42c54c1cfd3f33dace0b50537
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < 15dd3429f0e76ca071657e480cb7e6ff3a1af730
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < 7141331f2d245efc07175802a6bf76badec871ed
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < 95fec47cdbf747b81ab22affd7252dda6050ad0c
- affected 6640b5df1a38801be6d0595c8cd2177d968d7ee0 – < 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd
- affected 5.19
- unaffected < 5.19
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b3993f6dc106ff416c7a613c631e1e0af451aed7 (opens in a new tab)
- https://git.kernel.org/stable/c/f561392afb44a8a42c54c1cfd3f33dace0b50537 (opens in a new tab)
- https://git.kernel.org/stable/c/15dd3429f0e76ca071657e480cb7e6ff3a1af730 (opens in a new tab)
- https://git.kernel.org/stable/c/7141331f2d245efc07175802a6bf76badec871ed (opens in a new tab)
- https://git.kernel.org/stable/c/95fec47cdbf747b81ab22affd7252dda6050ad0c (opens in a new tab)
- https://git.kernel.org/stable/c/32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-115762 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99251)Record last updated .