VulnerabilityPublished 13 Jan 2026Updated 10 Nov 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical · fixed in a48e232210009be50591fdea8ba7c07b0f566a13 : patch Linux kernel as a priority.

Data as of 10 Nov 2026, 13:02 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Linux)	CVSS 3.1	9.1

Patch: Available – fixed in a48e232210009be50591fdea8ba7c07b0f566a13, 45ee0462b88396a0bd1df1991f801c89994ea72b, 5e5988736a95b1de7f91b10ac2575454b70e4897 +2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bba2556efad66e7eaa56fece13f7708caa1187f8, < a48e232210009be50591fdea8ba7c07b0f566a13	Fixed in a48e232210009be50591fdea8ba7c07b0f566a13
LinuxLinux	Affected ≥ bba2556efad66e7eaa56fece13f7708caa1187f8, < 45ee0462b88396a0bd1df1991f801c89994ea72b	Fixed in 45ee0462b88396a0bd1df1991f801c89994ea72b
LinuxLinux	Affected ≥ bba2556efad66e7eaa56fece13f7708caa1187f8, < 5e5988736a95b1de7f91b10ac2575454b70e4897	Fixed in 5e5988736a95b1de7f91b10ac2575454b70e4897
LinuxLinux	Affected ≥ bba2556efad66e7eaa56fece13f7708caa1187f8, < 4d0ceb7677e1c4616afb96abb4518f70b65abb0d	Fixed in 4d0ceb7677e1c4616afb96abb4518f70b65abb0d
LinuxLinux	Affected ≥ bba2556efad66e7eaa56fece13f7708caa1187f8, < 3f7823219407f2f18044c2b72366a48810c5c821	Fixed in 3f7823219407f2f18044c2b72366a48810c5c821
LinuxLinux	Affected =5.13	Fixed in–

AI-suggested

This vulnerability has been fixed in Linux kernel versions identified by the commits a48e232210009be50591fdea8ba7c07b0f566a13, 45ee0462b88396a0bd1df1991f801c89994ea72b, 5e5988736a95b1de7f91b10ac2575454b70e4897, 4d0ceb7677e1c4616afb96abb4518f70b65abb0d, and 3f7823219407f2f18044c2b72366a48810c5c821. Users should upgrade from version 5.13 to a fixed kernel release containing these commits to remediate the issue. No other mitigations or workarounds are indicated.

Description

A critical vulnerability in the Linux kernel's stmmac network driver causes a crash when handling zero copy XDP_TX actions. The issue arises from improper handling of memory types in the transmission path, leading to invalid memory mappings and kernel panic. This flaw affects Linux kernel version 5.13 and has been fixed in subsequent commits.

Impact

Exploitation of this vulnerability results in a kernel crash (kernel panic), causing denial of service on affected systems running Linux kernel version 5.13. The CVSS score of 9.1 indicates a critical severity with network attack vector, no privileges required, and no user interaction needed. The impact is limited to availability disruption; confidentiality and integrity are not affected.

Summary

CVE-2025-71095 addresses a crash issue in the Linux kernel's stmmac driver related to zero copy XDP_TX actions. The vulnerability occurs because the function stmmac_xdp_xmit_back() does not verify the memory type of the xdp_buff converted to xdp_frame, always assuming a page pool memory type. When the memory type is MEM_TYPE_PAGE_ORDER0 (from zero copy XSK pool), this leads to invalid DMA mappings and a kernel crash. The problem manifests as a kernel paging request failure and a fatal exception in interrupt context. The fix involves checking the xdp_buff memory type in stmmac_xdp_xmit_back() to ensure correct handling and prevent the crash.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 13:02 UTC

Technical details

References

Community reviews

Related threats