netfilter: nft_payload: fix mask build for partial field offload
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a5d45bc0dc50f9dd83703510e9804d813a9cac32 · < 16b553c46e347bc9de9946c4960654d5884a86de| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_payload: fix mask build for partial field offload
nft_payload_offload_mask() builds the offload match mask for a payload expression that covers only part of a header field. For a partial IPv6 address match (field_len = 16, priv_len = 1) that shift is 1 << 120, which is undefined on the 32-bit int operand. It also trims only one word, so the remaining words stay 0xffffffff (and when priv_len is a multiple of 4 the trim is skipped entirely), leaving the mask covering more bytes than the rule matches.
UBSAN: shift-out-of-bounds in net/netfilter/nft_payload.c:278:20 shift exponent 120 is too large for 32-bit type 'int' ...
The match is byte-granular and struct nft_data is zero-initialised, so the correct mask is simply the first priv_len bytes set to 0xff. Set those bytes directly and drop the word/shift trimming; this removes the undefined shift and no longer over-masks the trailing bytes.
From the CVE record · Linux
The Linux kernel’s nft_payload offload mask can cover more bytes than a rule matches when the rule matches only part of a header field. A partial IPv6 address match can also trigger an undefined shift. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running the Linux kernel with netfilter payload-match offload should check their systems; affected versions are not specified.