Description
In the Linux kernel, the following vulnerability has been resolved:

rtase: Workaround for TX hang caused by hardware packet parsing

The hardware performs packet parsing before packet transmission.
Parsing incomplete IPv4, IPv6, TCP, or UDP headers may trigger a TX
hang because the hardware parser expects additional protocol header
data that is not present in the packet.

The hardware performs additional PTP parsing on UDP packets identified
by destination ports 319/320 at the expected UDP destination port
offset.

If such a packet has transport data smaller than RTASE_MIN_PAD_LEN,
the hardware parser expects additional packet data and may trigger a
TX hang.

To avoid these hardware issues, the driver applies the following
workarounds.

Drop malformed packets that may trigger this hardware issue before
transmission.

For IPv4 non-initial fragments, the hardware does not check the
fragment offset before parsing the expected transport header location.
As a result, these packets are still subject to transport header
parsing even though they do not contain a transport header. If the
transport data is shorter than the minimum transport header required
by the hardware parser, pad the transport data to the minimum
transport header length required by the hardware parser. Packets that
also match the hardware PTP parsing conditions continue to follow the
corresponding workaround.

For IPv6 fragmented packets, neither of the above hardware issues
occurs because the hardware only continues packet parsing when the
IPv6 Base Header Next Header field directly indicates UDP. Packets
carrying a Fragment Header do not continue through the subsequent
packet parsing stages.

For packets identified for hardware PTP parsing, pad the transport
data so it reaches RTASE_MIN_PAD_LEN before transmission.
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability originates in the Linux kernel’s handling of hardware packet parsing during transmission. When the hardware receives a packet with incomplete or malformed IPv4, IPv6, TCP, or UDP headers, it mistakenly expects additional data that is not present. This mismatch can trigger a transmit (TX) hang, effectively blocking the networking stack and causing a denial of service. The flaw is in the driver’s lack of proper bounds checking and handling for fragmented packets and packets destined for hardware PTP parsing, leading the hardware parser to overread packet data. The impact is a local or remote DoS that can be triggered by sending specially crafted packets to the host, as the hardware will lock up in a TX state until it times out or is reset.

Affected Systems

Affected systems include all Linux kernel users that have not applied the rtase TX hang workaround. Vendors noted are generic Linux distributions, covering any kernel image before the patch that drops malformed packets and pads transport data for fragments and PTP‑eligible packets. No specific version information is listed, so any kernel not containing the recent rtase changes is potentially vulnerable.

Risk and Exploitability

The exploit can be performed remotely by inserting crafted network traffic on any interface that forwards packets to the hardware device. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog, indicating limited publicly confirmed exploitation. The CVSS score is not provided, but the nature of a TX hang suggests a high severity DoS risk. The attacker must be able to send packets that the kernel forwards to the hardware, which is typical for network-facing hosts. The lack of a published public exploit does not diminish the risk; a motivated actor could easily replicate the conditions described by the kernel maintainers.

Generated by OpenCVE AI on August 10, 2026 at 19:18 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the rtase TX hang workaround. The update should drop malformed packets and pad the transport data for IPv4 fragments and packets meeting PTP parsing conditions.
  • If building a custom kernel or using an older distribution, apply the specific patch that implements these workarounds for the RTASE driver. Verify the patch is applied by checking the kernel log for the workaround messages.
  • After updating or patching, monitor system logs for repeated TX hang incidents and ensure the network stack remains responsive. If an update is not immediately possible, temporarily mitigate by filtering or dropping packets that match the malformed patterns at a firewall or ingress policy before they reach the host.

Generated by OpenCVE AI on August 10, 2026 at 19:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 19:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119
CWE-770

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: rtase: Workaround for TX hang caused by hardware packet parsing The hardware performs packet parsing before packet transmission. Parsing incomplete IPv4, IPv6, TCP, or UDP headers may trigger a TX hang because the hardware parser expects additional protocol header data that is not present in the packet. The hardware performs additional PTP parsing on UDP packets identified by destination ports 319/320 at the expected UDP destination port offset. If such a packet has transport data smaller than RTASE_MIN_PAD_LEN, the hardware parser expects additional packet data and may trigger a TX hang. To avoid these hardware issues, the driver applies the following workarounds. Drop malformed packets that may trigger this hardware issue before transmission. For IPv4 non-initial fragments, the hardware does not check the fragment offset before parsing the expected transport header location. As a result, these packets are still subject to transport header parsing even though they do not contain a transport header. If the transport data is shorter than the minimum transport header required by the hardware parser, pad the transport data to the minimum transport header length required by the hardware parser. Packets that also match the hardware PTP parsing conditions continue to follow the corresponding workaround. For IPv6 fragmented packets, neither of the above hardware issues occurs because the hardware only continues packet parsing when the IPv6 Base Header Next Header field directly indicates UDP. Packets carrying a Fragment Header do not continue through the subsequent packet parsing stages. For packets identified for hardware PTP parsing, pad the transport data so it reaches RTASE_MIN_PAD_LEN before transmission.
Title rtase: Workaround for TX hang caused by hardware packet parsing
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T11:58:40.224Z

Reserved: 2026-07-30T09:28:09.369Z

Link: CVE-2026-68120

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T19:30:17Z

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer

  • CWE-770

    Allocation of Resources Without Limits or Throttling