# CVE-2026-23054: net: hv_netvsc: reject RSS hash key programming without RX indirection table

> A local attacker with high privileges can cause a system hang in the Linux kernel by programming RSS hash keys without an RX indirection table.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-77226, BELL-CVE-2026-23054, DEBIAN-CVE-2026-23054, GHSA-64h7-35x7-95w2, ROOT-OS-DEBIAN-11-CVE-2026-23054, ROOT-OS-UBUNTU-2204-CVE-2026-23054, ROOT-OS-UBUNTU-2404-CVE-2026-23054, UBUNTU-CVE-2026-23054

## What is CVE-2026-23054?

CVE-2026-23054 is a denial of service vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

net: hv_netvsc: reject RSS hash key programming without RX indirection table

RSS configuration requires a valid RX indirection table. When the device
reports a single receive queue, rndis_filter_device_add() does not
allocate an indirection table, accepting RSS hash key updates in this
state leads to a hang.

Fix this by gating netvsc_set_rxfh() on ndc->rx_table_sz and return
-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device
capabilities and prevents incorrect behavior.

## Which versions are affected by CVE-2026-23054?


## How do I fix CVE-2026-23054?

Apply the vendor's patch.

## Is CVE-2026-23054 being exploited?

There is no known exploitation of CVE-2026-23054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23054 and fix it if it is affected.

What it is: CVE-2026-23054 is a denial of service vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23054 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23054/ (Markdown: https://insights.sbomify.com/CVE-2026-23054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23054
- OSV: https://osv.dev/vulnerability/CVE-2026-23054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23054/
Summaries are generated and may contain mistakes; the official description above is the record.