# CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources

> A flaw in the Linux kernel hns3 driver causes uninitialized memory access, potentially leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-71064, DEBIAN-CVE-2025-71064, GHSA-w787-fq27-wmmf, ROOT-OS-DEBIAN-11-CVE-2025-71064, ROOT-OS-DEBIAN-12-CVE-2025-71064, ROOT-OS-DEBIAN-13-CVE-2025-71064, ROOT-OS-UBUNTU-2204-CVE-2025-71064, ROOT-OS-UBUNTU-2404-CVE-2025-71064, UBUNTU-CVE-2025-71064

## What is CVE-2025-71064?

CVE-2025-71064 is a vulnerability in Linux, published on 13 Jan 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: 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.

## Which versions are affected by CVE-2025-71064?


## How do I fix CVE-2025-71064?

Apply the vendor's patch.

## Is CVE-2025-71064 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71064 and fix it if it is affected.

What it is: CVE-2025-71064 is a vulnerability in Linux, published on 13 Jan 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-2025-71064 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-2025-71064/ (Markdown: https://insights.sbomify.com/CVE-2025-71064/index.md)
```

## Sources

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

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