Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 15dd3429f0e76ca071657e480cb7e6ff3a1af730, 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd, 7141331f2d245efc07175802a6bf76badec871ed.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 15dd3429f0e76ca071657e480cb7e6ff3a1af730, 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd, 7141331f2d245efc07175802a6bf76badec871ed or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Nov 3, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99251

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.19affected
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before b3993f6dc106ff416c7a613c631e1e0af451aed7affected · git
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before f561392afb44a8a42c54c1cfd3f33dace0b50537affected · git
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before 15dd3429f0e76ca071657e480cb7e6ff3a1af730affected · git
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before 7141331f2d245efc07175802a6bf76badec871edaffected · git
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before 95fec47cdbf747b81ab22affd7252dda6050ad0caffected · git
    • 6640b5df1a38801be6d0595c8cd2177d968d7ee0 and later · before 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fdaffected · git
    • before 5.19not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.161 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.115-16.12.115-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99249Nov 3, 2026 · pid_namespace: make zap_pid_ns_processes() freezable
    0Monitor
  • ← EarlierCVE-2026-99250Nov 3, 2026 · printk: Postpone kthread startup
    0Monitor
  • Later →CVE-2026-99253Nov 3, 2026 · io_uring/cancel: rearm local work wake up before sleep
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux15dd3429f0e76ca071657e480cb7e6ff3a1af730Vendor (CNA)
Linux Linux32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fdVendor (CNA)
Linux Linux7141331f2d245efc07175802a6bf76badec871edVendor (CNA)
Linux Linux95fec47cdbf747b81ab22affd7252dda6050ad0cVendor (CNA)
Linux Linuxb3993f6dc106ff416c7a613c631e1e0af451aed7Vendor (CNA)
Linux Linuxf561392afb44a8a42c54c1cfd3f33dace0b50537Vendor (CNA)
debian:linux6.12.115-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 7, 2026+4 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records