In the Linux kernel, the following vulnerability has been resolved:
net: libwx: fix Tx L4 checksum
The hardware only supports L4 checksum offload for TCP/UDP/SCTP protocol.
There was a bug to set Tx checksum flag for the other protocol that results
in Tx ring hang. Fix to compute software checksum for these packets.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22101 is a Linux kernel network-driver bug. For certain transmitted packets, the driver could ask hardware to checksum unsupported protocols, causing the transmit ring to hang. Business impact is most likely network disruption on affected systems, but public sources do not provide severity, CVSS, or evidence of active exploitation.
Executive priority
Treat as a targeted reliability and availability issue. Patch during the next appropriate kernel maintenance window, sooner for systems where affected network hardware supports critical services.
Technical view
The issue is in Linux kernel net/libwx Tx L4 checksum handling. Hardware supports checksum offload only for TCP, UDP, and SCTP, but the driver set the Tx checksum flag for other protocols. The upstream fix uses software checksum handling for unsupported packets. Kernel stable commits are referenced as fixes.
Likely exposure
Exposure likely requires Linux systems running affected kernel versions with the relevant libwx-supported network hardware or driver path. The CVE record lists Linux kernel versions as affected, but distro-specific package status is not provided.
Exploitation context
CISA KEV is false, and the provided sources do not report active exploitation or a public exploit. The plausible impact is denial of service or network transmit failure when affected packet types are sent through the vulnerable driver.
Researcher notes
The public record lacks CVSS, CWE, exploitability details, and distro mapping. Analysis should focus on commit inclusion, hardware applicability, and whether local workloads can generate unsupported L4 checksum-offload traffic through libwx.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check your distribution or appliance vendor advisory for backported patches.
Prioritize systems using libwx-supported network hardware in production paths.
Monitor affected systems for network transmit hangs until patched.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Identify hosts using the affected libwx network driver path.
Confirm installed kernels include the referenced stable commits or vendor backports.
Review network incidents for Tx ring hangs on relevant hosts.
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-22101 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.