netfilter: handle unreadable frags
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: handle unreadable frags
sashiko reports: When an skb with unreadable fragments (such as from devmem TCP, where skb_frags_readable(skb) returns false) is processed by the u32 module, skb_copy_bits() will safely return a negative error code [..]
xt_u32: bail out with hotdrop in this case. gather_frags: return -1, just as if we had no fragment header. nfnetlink_queue: restrict to the linear part. nfnetlink_log: restrict to the linear part.
v2: - skb_zerocopy helpers don't copy readable flag, i.e. nfnetlink_queue is broken too xt_u32 shouldn't return true if hotdrop was set.
From the CVE record · Linux
Linux kernel netfilter can mishandle packet fragments that cannot be read, including those from devmem TCP. The u32 module can encounter a read error, while nfnetlink_queue and nfnetlink_log need to limit processing to the readable linear portion. The input does not specify what an attacker can achieve or whether exploitation requires network or local access, authentication, or user interaction.
Engineers running the Linux kernel should check their netfilter exposure; affected versions are not specified.