# CVE-2026-99251: Drivers: hv: Avoid infinite retry loop in init_vp_index()

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < b3993f6dc106ff416c7a613c631e1e0af451aed7 (affected, git); ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < f561392afb44a8a42c54c1cfd3f33dace0b50537 (affected, git); ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < 15dd3429f0e76ca071657e480cb7e6ff3a1af730 (affected, git); ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < 7141331f2d245efc07175802a6bf76badec871ed (affected, git); ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < 95fec47cdbf747b81ab22affd7252dda6050ad0c (affected, git); ≥ 6640b5df1a38801be6d0595c8cd2177d968d7ee0; < 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd (affected, git). Source: CNA: Linux
- Linux / Linux: 5.19 (affected); ≥ 0; < 5.19 (unaffected, semver); ≥ 6.1.191; ≤ 6.1.* (unaffected, semver); ≥ 6.6.161; ≤ 6.6.* (unaffected, semver); ≥ 6.12.115; ≤ 6.12.* (unaffected, semver); ≥ 6.18.59; ≤ 6.18.* (unaffected, semver); ≥ 7.2.13; ≤ 7.2.* (unaffected, semver); ≥ 7.3; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/b3993f6dc106ff416c7a613c631e1e0af451aed7 (CNA: Linux)

- https://git.kernel.org/stable/c/f561392afb44a8a42c54c1cfd3f33dace0b50537 (CNA: Linux)

- https://git.kernel.org/stable/c/15dd3429f0e76ca071657e480cb7e6ff3a1af730 (CNA: Linux)

- https://git.kernel.org/stable/c/7141331f2d245efc07175802a6bf76badec871ed (CNA: Linux)

- https://git.kernel.org/stable/c/95fec47cdbf747b81ab22affd7252dda6050ad0c (CNA: Linux)

- https://git.kernel.org/stable/c/32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99251; retrieved 2026-11-03; source updated 2026-11-03

Revision: 3241250da81f57ce82aba55e45f804db6c07d6bd03da394ba7791a764ab78539

Canonical: https://y2.dev/cve/CVE-2026-99251

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.