CVE-2025-71064: Linux kernel · net: hns3: using the num_tqps in the vf driver to apply for resources
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c149decd8c18ae6acdd7a6041d74507835cf26e6 : update Linux kernel when convenient.
Data as of 10 Nov 2026, 13:18 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in c149decd8c18ae6acdd7a6041d74507835cf26e6, c2a16269742e176fccdd0ef9c016a233491a49ad, bcefdb288eedac96fd2f583298927e9c6c481489 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A patch is available and has been applied to the Linux kernel to fix this issue by correcting the allocation logic. Users should update to the fixed kernel versions containing the patch to remediate this vulnerability. Since this is a Linux kernel vulnerability, the vendor manages remediation for cloud-hosted services. Check vendor advisories for confirmation and apply official updates.
Description
A vulnerability in the Linux kernel's hns3 network driver was identified where inconsistent allocation sizes for resource arrays could lead to uninitialized elements. Specifically, the vf driver used differing counts for allocating hdev->htqp and kinfo->tqp arrays, causing some elements to remain uninitialized. This issue was fixed by ensuring both arrays are allocated using the same count, hdev->num_tqps, to guarantee proper initialization.
References
- git.kernel.org/stable/c/c149decd8c18ae6acdd7a6041d74507835cf26e6 (opens in a new tab)
- git.kernel.org/stable/c/bcefdb288eedac96fd2f583298927e9c6c481489 (opens in a new tab)
- git.kernel.org/stable/c/6cd8a2930df850f4600fe8c57d0662b376520281 (opens in a new tab)
- git.kernel.org/stable/c/1956d47a03eb625951e9e070db39fe2590e27510 (opens in a new tab)
- git.kernel.org/stable/c/429f946a7af3fbf08761d218746cd4afa80a7954 (opens in a new tab)
- git.kernel.org/stable/c/62f28d79a6186a602a9d926a2dbb5b12b6867df7 (opens in a new tab)
- git.kernel.org/stable/c/c2a16269742e176fccdd0ef9c016a233491a49ad (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)