Linux kernel incorrect header offsets in BPF flow dissector
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 · < cc18eb0e9941162c03f03f411ed7f6c339d91fa0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()
bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).
If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.
This is the same class of bug as the one fixed in commit 99bda1ecbd56 ("flow_dissector: avoid u16 truncation of skb->len when computing thoff"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.
struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.
Found by sashiko while reviewing the commit above.
From the CVE record · Linux
The Linux kernel’s BPF flow dissector can truncate the packet header length when it exceeds 65,535 bytes, forcing otherwise valid offsets to zero. This can cause incorrect packet parsing when a BPF flow dissector handles such a packet; the input does not establish an attack path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels that use a BPF flow dissector should check their kernel; affected versions are not specified.