VYPR
Unrated severityNVD Advisory· Published Jan 13, 2026· Updated Apr 15, 2026

CVE-2025-71064

CVE-2025-71064

Description

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

net: hns3: using the num_tqps in the vf driver to apply for resources

Currently, hdev->htqp is allocated using hdev->num_tqps, and kinfo->tqp is allocated using kinfo->num_tqps. However, kinfo->num_tqps is set to min(new_tqps, hdev->num_tqps); Therefore, kinfo->num_tqps may be smaller than hdev->num_tqps, which causes some hdev->htqp[i] to remain uninitialized in hclgevf_knic_setup().

Thus, this patch allocates hdev->htqp and kinfo->tqp using hdev->num_tqps, ensuring that the lengths of hdev->htqp and kinfo->tqp are consistent and that all elements are properly initialized.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In the Linux kernel's HNS3 driver, a resource allocation mismatch causes uninitialized queue pointers, potentially leading to kernel Oops or data corruption.

Vulnerability

Analysis

CVE-2025-71064 describes a resource allocation mismatch in the Linux kernel's HNS3 network driver, specifically in the virtual function (VF) handling code. The driver allocates two arrays: hdev->htqp using hdev->num_tqps and kinfo->tqp using kinfo->num_tqps. However, kinfo->num_tqps is set to min(new_tqps, hdev->num_tqps), which can be smaller than hdev->num_tqps. This leads to a scenario where some elements of hdev->htqp[index] remain uninitialized because the loop in hclgevf_knic_setup() only iterates up to kinfo->num_tqps [1].

Exploitability

An attacker with the ability to trigger the knic_setup path in the HNS3 VF driver—likely via network configuration changes or device hotplug—could cause the kernel to access uninitialized memory. This does not require remote network access but may require local capabilities to manipulate network interfaces [2].

Impact

When the driver attempts to use the uninitialized hdev->htqp entries (e.g., for queue operations), the kernel may dereference a wild pointer, causing a kernel panic (Oops) or memory corruption. This could lead to denial of service (DoS) or, in principle, system instability [3]. The privilege required is low (local user with netlink/sysfs access), and availability impact is high.

Mitigation

The fix, merged into the mainline kernel, changes both allocations to consistently use hdev->num_tqps, ensuring all htqp entries are properly initialized. Users should apply the corresponding stable kernel updates for their distribution [1][2]. No workaround is available aside from upgrading.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

7

News mentions

0

No linked articles in our index yet.