LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix the crash issue for zero copy XDP_TX action There is a crash issue when running zero copy XDP_TX action, the crash log is shown below. [ 216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000 [ 216.187524] Internal error: Oops: 0000000096000144 [#1] SMP [ 216.301694] Call trace: [ 216.304130] dcache_clean_poc+0x20/0x38 (P) [ 216.308308] __dma_sync_single_for_device+0x1bc/0x1e0 [ 216.313351] stmmac_xdp_xmit_xdpf+0x354/0x400 [ 216.317701] __stmmac_xdp_run_prog+0x164/0x368 [ 216.322139] stmmac_napi_poll_rxtx+0xba8/0xf00 [ 216.326576] __napi_poll+0x40/0x218 [ 216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt For XDP_TX action, the xdp_buff is converted to xdp_frame by xdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame depends on the memory type of the xdp_buff. For page pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy XSK pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the memory type and always uses the page pool type, this leads to invalid mappings and causes the crash. Therefore, check the xdp_buff memory type in stmmac_xdp_xmit_back() to fix this issue.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems using the stmmac Ethernet driver when zero-copy XDP_TX traffic is processed. The business impact is availability loss, especially for embedded or network-facing systems using affected kernels and this datapath.

Executive priority

Treat as a targeted availability risk, not a broad emergency. Patch systems using stmmac and zero-copy XDP first, especially operational technology or edge devices where crashes disrupt service.

Technical view

stmmac_xdp_xmit_back() assumed page-pool-backed XDP frames. Zero-copy XSK-backed buffers can become MEM_TYPE_PAGE_ORDER0 frames, causing invalid DMA mapping handling and a kernel paging fault during XDP_TX processing.

Likely exposure

Exposure appears limited to Linux systems using the stmmac Ethernet driver with zero-copy XDP_TX or related AF_XDP/XSK configuration. Generic Linux hosts without this driver or feature path are less likely exposed.

Exploitation context

The source bundle shows a crash and kernel panic condition, but provides no evidence of active exploitation. KEV is false, and no public exploit status is cited.

Researcher notes

The evidence supports a memory-type handling bug in the stmmac XDP transmit path. Affected-version precision is incomplete in the bundle, so confirm exact fixed ranges through kernel stable commits and vendor advisories.

Mitigation direction

  • Update affected Linux kernels to vendor-provided fixed stable releases or fixed commits.
  • Check Siemens guidance for affected Siemens products before operational changes.
  • Temporarily avoid zero-copy XDP_TX on stmmac interfaces until patched.
  • Prioritize embedded, OT, and edge devices using stmmac networking.

Validation and detection

  • Inventory Linux assets for stmmac driver usage and affected kernel versions.
  • Check whether XDP_TX, AF_XDP, or zero-copy XSK pools are enabled.
  • Compare deployed kernels against the cited stable kernel fixes.
  • Review crash logs for stmmac_xdp_xmit_xdpf or kernel paging faults.
Prepared
Confidence
medium
Sources
8

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-71095 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
7Source 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
LinuxLinuxbba2556efad66e7eaa56fece13f7708caa1187f8, bba2556efad66e7eaa56fece13f7708caa1187f8, bba2556efad66e7eaa56fece13f7708caa1187f8, bba2556efad66e7eaa56fece13f7708caa1187f8, bba2556efad66e7eaa56fece13f7708caa1187f8unaffected
LinuxLinux5.13, 0, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 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.