Linux kernel packet header corruption via nft_payload checksum offsets
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 |
|
|
7.3.27.4-rc1In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_payload: restrict checksum offsets to known values
We need to prevent userspace from corrupting e.g. tcp->doff, because many locations in conntrack and conntrack helpers rely on nf_conntrack_in() having validated the packet headers. nft_payload allows to alter headers later which invalidates this assumption.
The 'Fixes' commit restricts writes to safe fields, but there is another side channel: the checksum location.
Restrict this too. Reported via sashiko/gemini.
From the CVE record · Linux
The Linux kernel's netfilter nft_payload component did not restrict checksum offsets to known values. Userspace able to configure nft_payload writes could use the checksum location to corrupt packet headers after conntrack validated them, invalidating assumptions made by conntrack and its helpers. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel should check whether their versions include the netfilter nft_payload fix; affected versions are not specified.