CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Fixed version: Linux Linux 1956d47a03eb625951e9e070db39fe2590e27510, 429f946a7af3fbf08761d218746cd4afa80a7954, 62f28d79a6186a602a9d926a2dbb5b12b6867df7.
Low priority for now. Upgrade to Linux Linux 1956d47a03eb625951e9e070db39fe2590e27510, 429f946a7af3fbf08761d218746cd4afa80a7954, 62f28d79a6186a602a9d926a2dbb5b12b6867df7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.16affected
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before c149decd8c18ae6acdd7a6041d74507835cf26e6affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before bcefdb288eedac96fd2f583298927e9c6c481489affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before 6cd8a2930df850f4600fe8c57d0662b376520281affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before 1956d47a03eb625951e9e070db39fe2590e27510affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before 429f946a7af3fbf08761d218746cd4afa80a7954affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before 62f28d79a6186a602a9d926a2dbb5b12b6867df7affected · git
- e2cb1dec9779ba2d89302a653eb0abaeb8682196 and later · before c2a16269742e176fccdd0ef9c016a233491a49adaffected · git
- before 4.16not affected · semver
- 5.10.248 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.3-1 | 6.18.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68820Jan 13, 2026 · ext4: xattr: fix null pointer deref in ext4_raw_inode()0Monitor
- ← EarlierCVE-2025-68822Jan 13, 2026 · Input: alps - fix use-after-free bugs caused by dev3_register_work31Monitor
- Later →CVE-2025-71140Jan 14, 2026 · media: mediatek: vcodec: Use spinlock for context list protection lock0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1956d47a03eb625951e9e070db39fe2590e27510 | Vendor (CNA) |
| Linux Linux | 429f946a7af3fbf08761d218746cd4afa80a7954 | Vendor (CNA) |
| Linux Linux | 62f28d79a6186a602a9d926a2dbb5b12b6867df7 | Vendor (CNA) |
| Linux Linux | 6cd8a2930df850f4600fe8c57d0662b376520281 | Vendor (CNA) |
| Linux Linux | bcefdb288eedac96fd2f583298927e9c6c481489 | Vendor (CNA) |
| Linux Linux | c149decd8c18ae6acdd7a6041d74507835cf26e6 | Vendor (CNA) |
| Linux Linux | c2a16269742e176fccdd0ef9c016a233491a49ad | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/429f946a7af3fbf08761d218746cd4afa80a7954
- git.kernel.org/stable/c/62f28d79a6186a602a9d926a2dbb5b12b6867df7
- git.kernel.org/stable/c/6cd8a2930df850f4600fe8c57d0662b376520281
- git.kernel.org/stable/c/bcefdb288eedac96fd2f583298927e9c6c481489
- git.kernel.org/stable/c/c149decd8c18ae6acdd7a6041d74507835cf26e6
- git.kernel.org/stable/c/c2a16269742e176fccdd0ef9c016a233491a49ad
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.