---
id: CVE-2026-99258
title: 'x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index()'
summary: |-
  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 functi…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 3d12349ade541eefde0e71bf5c4aa7aa04c52a79 <
    bdba5f1b8bd0d18b1df61f769b559ed272902489
  - >-
    Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 <
    2b561786c9076a892ef8b8f416c9828bc87ed44f
  - >-
    Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 <
    bc8ca0f4769627ae7d04e7ffdbd20de4f27a9bf9
  - >-
    Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 <
    7b74c117e2aac78e0f723e1c9c3644451c56b0d9
  - Linux cb002d6c8f06d6061e84b2109cb84416107a9fb9
  - Linux >= 6.12.41 < 6.12.115
  - Linux >= 6.15.3 < 6.16
  - Linux 6.16
published: '2026-11-03'
updated: '2026-11-03'
sourceUpdated: '2026-11-03T11:40:46.409Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-99258'
references:
  - url: 'https://git.kernel.org/stable/c/bdba5f1b8bd0d18b1df61f769b559ed272902489'
  - url: 'https://git.kernel.org/stable/c/2b561786c9076a892ef8b8f416c9828bc87ed44f'
  - url: 'https://git.kernel.org/stable/c/bc8ca0f4769627ae7d04e7ffdbd20de4f27a9bf9'
  - url: 'https://git.kernel.org/stable/c/7b74c117e2aac78e0f723e1c9c3644451c56b0d9'
tags:
  - cve.org
epss: 0.00192
epssPercentile: 0.08872
ingestedAt: '2026-11-05T19:30:42.940Z'
---

## Overview

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.

## Affected

- `Linux >= 3d12349ade541eefde0e71bf5c4aa7aa04c52a79 < bdba5f1b8bd0d18b1df61f769b559ed272902489`
- `Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 < 2b561786c9076a892ef8b8f416c9828bc87ed44f`
- `Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 < bc8ca0f4769627ae7d04e7ffdbd20de4f27a9bf9`
- `Linux >= 86c48271e0d60c82665e9fd61277002391efcef7 < 7b74c117e2aac78e0f723e1c9c3644451c56b0d9`
- `Linux cb002d6c8f06d6061e84b2109cb84416107a9fb9`
- `Linux >= 6.12.41 < 6.12.115`
- `Linux >= 6.15.3 < 6.16`
- `Linux 6.16`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.