LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71112: net: hns3: add VLAN id validation before using

In the Linux kernel, the following vulnerability has been resolved: net: hns3: add VLAN id validation before using Currently, the VLAN id may be used without validation when receive a VLAN configuration mailbox from VF. The length of vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause out-of-bounds memory access once the VLAN id is bigger than or equal to VLAN_N_VID. Therefore, VLAN id needs to be checked to ensure it is within the range of VLAN_N_VID.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the hns3 network driver. A virtual function can send VLAN configuration data with an invalid VLAN ID, and the driver may use it before checking bounds. That can lead to out-of-bounds memory access on affected hosts.

Executive priority

Treat as a targeted kernel maintenance item. Prioritize patching virtualization or appliance hosts that use hns3 networking. Broader urgency is unclear because severity, exploitability, and active exploitation evidence are not provided.

Technical view

The hns3 PF mailbox VLAN path failed to validate a VF-supplied VLAN ID before indexing vlan_del_fail_bmap, whose size is based on VLAN_N_VID. VLAN IDs greater than or equal to VLAN_N_VID can trigger out-of-bounds memory access. Linux stable commits add the missing validation.

Likely exposure

Exposure appears limited to Linux systems using the hns3 network driver, especially environments using virtual functions and VLAN configuration through the PF/VF mailbox path.

Exploitation context

The source bundle does not report active exploitation, public exploit code, CVSS, CWE, or confirmed impact beyond out-of-bounds memory access. KEV status is false.

Researcher notes

The root issue is missing VLAN ID bounds validation before bitmap access in hns3 VLAN mailbox handling. Analysis should focus on VF-to-PF control paths and whether the resulting out-of-bounds access is only denial-of-service or has broader memory-safety impact.

Mitigation direction

  • Apply a Linux kernel update that includes the referenced stable fixes.
  • Check distribution and hardware vendor advisories for packaged kernel guidance.
  • Prioritize hosts using hns3 devices with virtual functions enabled.
  • Review the Siemens advisory if Siemens products are in scope.

Validation and detection

  • Inventory Linux hosts for hns3 driver and affected kernel exposure.
  • Confirm whether hns3 virtual functions are enabled or assigned to tenants.
  • Verify the running kernel includes one of the referenced stable fixes.
  • Track vendor advisories for any product-specific affected version mapping.
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-71112 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
LinuxLinuxfe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219, fe4144d47eef8453459c53a34e9d5940a3e6c219unaffected
LinuxLinux5.3, 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.