net: gue: reject invalid REMCSUM offsets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fe881ef11cf0220f118816181930494d484c4883 · < 40aeafbcbc7bc4018e8f74bbbb4d29ed8846f57f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: gue: reject invalid REMCSUM offsets
The REMCSUM option carries an absolute checksum start and checksum field offset. gue_remcsum() passes them to skb_remcsum_process(), whose partial path stores offset - start in the u16 skb->csum_offset variable. If offset is less than start, this underflows.
A forwarded packet can retain CHECKSUM_PARTIAL and reach a NETIF_F_HW_CSUM driver which trusts the metadata, leading skb_copy_and_csum_dev() to write two bytes about 64 KiB beyond the destination buffer.
Reject reversed tuples in validate_gue_flags(), after the existing length validation, so all GUE parsers enforce the ordering in one place.
From the CVE record · Linux
The Linux kernel accepts GUE REMCSUM offsets in the wrong order, causing a checksum offset to underflow. A forwarded packet with those offsets can trigger an out-of-bounds write if it retains CHECKSUM_PARTIAL and reaches a NETIF_F_HW_CSUM driver. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel should check whether their version includes the GUE REMCSUM fix; affected versions are not specified.