Menu

Star on GitHub · 3.2k

CVE-2026-23054

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…

Published Feb 4, 2026EPSS 0.20%

Overview

CVE-2026-23054 is a known-severity vulnerability. It was published on February 4, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-23054?

CVE-2026-23054 is a known-severity vulnerability. It was published on February 4, 2026.

How severe is CVE-2026-23054?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-23054?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-23054?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-23054 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.