CVE-2026-99258

Unknown

Last modified

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

Description

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 Software

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

VendorProductVersions
LinuxLinux>= 3d12349ade541eefde0e71bf5c4aa7aa04c52a79, < bdba5f1b8bd0d18b1df61f769b559ed272902489; >= 86c48271e0d60c82665e9fd61277002391efcef7, < 2b561786c9076a892ef8b8f416c9828bc87ed44f; >= 86c48271e0d60c82665e9fd61277002391efcef7, < bc8ca0f4769627ae7d04e7ffdbd20de4f27a9bf9; >= 86c48271e0d60c82665e9fd61277002391efcef7, < 7b74c117e2aac78e0f723e1c9c3644451c56b0d9; cb002d6c8f06d6061e84b2109cb84416107a9fb9; >= 6.12.41, < 6.12.115; >= 6.15.3, < 6.16
LinuxLinux6.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-99258?
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.
How severe is CVE-2026-99258?
Severity scoring for CVE-2026-99258 is pending analysis.
How do I fix CVE-2026-99258?
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

Are you affected by CVE-2026-99258?

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

Scan your code now

Source: NVD / NIST