gue: validate REMCSUM private option length
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c1aa8347e73e4092411fbd96cc59531fb7e76d04 · < 4a4a1d41c6e901e773bcf795f562a47fa71f692a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gue: validate REMCSUM private option length
GUE private flags can indicate that remote checksum offload metadata is present. The private flags field itself is accounted for by guehdr_flags_len(), but guehdr_priv_flags_len() currently returns 0 even when GUE_PFLAG_REMCSUM is set.
This lets a packet with only the private flags field pass validate_gue_flags(), after which gue_remcsum() and gue_gro_remcsum() read the missing REMCSUM start/offset fields from the following bytes.
Account for GUE_PLEN_REMCSUM when GUE_PFLAG_REMCSUM is present so that malformed packets are rejected during option validation.
From the CVE record · Linux
The Linux kernel does not account for the required REMCSUM fields when validating GUE private options. A malformed packet can pass validation, causing GUE processing to read missing fields from subsequent bytes. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.