rtase: Workaround for TX hang caused by hardware packet parsing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel rtase driver can trigger a transmission (TX) hang when hardware parses incomplete protocol headers or certain short UDP packets. The issue arises when affected packets are transmitted; the input does not specify whether triggering it requires local or network access, authentication, or user interaction.
Engineers running Linux systems that use the rtase driver should check their kernel; affected versions are not specified.