# CVE-2026-99258: x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index()

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

In the Linux kernel, the following vulnerability has been resolved:

x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index()

hv_apicid_to_vp_index() currently uses the per-cpu hypercall input
and output pages. This function is called when running in VTL2 and
when running in an SEV-SNP CoCo VM with no paravisor. In the former
case, the output page is allocated, but in the latter case it is
not, so the hypervisor stores the output VP index in memory that has
not been allocated by the guest.

Fix this by using the input page for both input and output. The
hypercall has very small input and output, so sharing the same
page for both is straightforward. An alternative fix is to
allocate the per-cpu output page when running in an SEV-SNP CoCo
guest, but this uses significantly more memory, particularly
with larger vCPUs counts.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 3d12349ade541eefde0e71bf5c4aa7aa04c52a79; < bdba5f1b8bd0d18b1df61f769b559ed272902489 (affected, git); ≥ 86c48271e0d60c82665e9fd61277002391efcef7; < 2b561786c9076a892ef8b8f416c9828bc87ed44f (affected, git); ≥ 86c48271e0d60c82665e9fd61277002391efcef7; < bc8ca0f4769627ae7d04e7ffdbd20de4f27a9bf9 (affected, git); ≥ 86c48271e0d60c82665e9fd61277002391efcef7; < 7b74c117e2aac78e0f723e1c9c3644451c56b0d9 (affected, git); cb002d6c8f06d6061e84b2109cb84416107a9fb9 (affected, git); ≥ 6.12.41; < 6.12.115 (affected, semver); ≥ 6.15.3; < 6.16 (affected, semver). Source: CNA: Linux
- Linux / Linux: 6.16 (affected); ≥ 0; < 6.16 (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/bdba5f1b8bd0d18b1df61f769b559ed272902489 (CNA: Linux)

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

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

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

## Provenance

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

Revision: 8a8c9805eea2762b82a97d8af4e1f95fb2d16bba4bb5ff2a2f7f732318456272

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

## 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.