cve.bz

CVE-2026-99251 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.59
  • Linux Linux: fixed in 7.2.13
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99251 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99251?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99251?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99251 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-99251

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99251](https://cve.bz/cve/badge/CVE-2026-99251.svg)](https://cve.bz/cve/CVE-2026-99251)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99251"><img src="https://cve.bz/cve/badge/CVE-2026-99251.svg" alt="CVE-2026-99251"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.19 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.59
Linux7.27.2.13
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99251
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99251
Debian13linux6.12.115-1DEBIAN-CVE-2026-99251
Debian14linux7.2.13-1DEBIAN-CVE-2026-99251
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99251
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99251
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99251
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-99251
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99251
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99251
Ubuntu26.10linux7.3.0-10.10UBUNTU-CVE-2026-99251
Ubuntu26.10linux-aws, linux-gcp, linux-azure and 2 more7.3.0-1004.4UBUNTU-CVE-2026-99251
Ubuntu26.10linux-azure-fde7.3.0-1004.5UBUNTU-CVE-2026-99251
Ubuntu26.10linux-riscv, linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-99251
UbuntuNvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99251
UbuntuPro:FIPS-updates:24.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99251
2 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.161.1-1AZL-112607
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99251
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99251
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99251

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

References

Check your stackJSON