LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver flaw in the HNS3 virtual-function network driver. A resource allocation mismatch can leave queue-pointer entries uninitialized. The public record does not provide CVSS, impact details, or exploitation evidence, so urgency depends on whether affected Linux kernels and HNS3 VF networking are present.

Executive priority

Do not treat this as internet-wide emergency based on the supplied evidence. Prioritize normal kernel patch governance, with faster handling for appliances, virtualized hosts, or industrial systems using HNS3 VF networking.

Technical view

The issue is in hns3 VF setup: hdev->htqp used hdev->num_tqps while kinfo->tqp used kinfo->num_tqps, which may be smaller after min(new_tqps, hdev->num_tqps). That can leave hdev->htqp[i] uninitialized during hclgevf_knic_setup(). Stable commits align allocation sizes to hdev->num_tqps.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the HNS3 VF driver path. The bundle lists Linux kernel versions and multiple stable commits, but provides no CPEs or complete downstream product mapping.

Exploitation context

No active exploitation is stated. KEV is false, and the provided sources do not describe public exploit activity, exploitability prerequisites, or a practical attack path. Treat this as a kernel reliability or potential memory-safety issue until vendor impact guidance clarifies severity.

Researcher notes

The key condition is inconsistent num_tqps allocation between hdev and kinfo structures in the hns3 VF driver. The bundle lacks CVSS, CWE, crash details, privilege context, and exploitability analysis, so validation should focus on driver reachability and fixed-commit presence.

Mitigation direction

  • Update to a Linux kernel package containing the referenced stable fix commits.
  • Check Siemens SSA-019113 if Siemens products are in scope.
  • Prioritize hosts using HNS3 virtual-function networking or related NIC drivers.
  • Use distribution or appliance vendor guidance for exact fixed package versions.

Validation and detection

  • Inventory Linux kernel versions against vendor fixed-version guidance.
  • Check whether hns3 or hclgevf driver components are present or loaded.
  • Confirm deployed kernel source or package includes one referenced stable commit.
  • Review virtualization and NIC configurations for HNS3 VF usage.
  • Track vendor advisories for severity, affected products, and regressions.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71064 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196, e2cb1dec9779ba2d89302a653eb0abaeb8682196unaffected
LinuxLinux4.16, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.