netfilter: flowtable: support IPIP tunnel with direct xmit
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: flowtable: support IPIP tunnel with direct xmit
The combination of IPIP tunnel with direct xmit, eg. bridge device, breaks because no dst_entry is provided to check the skb headroom and to set the iph->frag_off field. This leads to invalid dst usage and can trigger a crash in the tunnel transmit path.
Fix this by moving dst_cache and dst_cookie out of the runtime union so that they can be shared by neighbour, xfrm, and direct tunnel flows. For FLOW_OFFLOAD_XMIT_DIRECT tuples carrying tunnel metadata, preserve route state in these shared fields and release it through the common dst release path.
Since dst_entry is now available to the three supported xmit modes and dst_release() already deals with NULL dst, remove the xmit type check in nft_flow_dst_release(). Moreover, skip the check if the dst entry is NULL in nf_flow_dst_check() which is now the case for the direct xmit case.
Based on patch from Rein Wei <n05ec@lzu.edu.cn>.
From the CVE record · Linux
The Linux kernel netfilter flowtable can use an invalid destination entry when an IPIP tunnel uses direct transmit, such as through a bridge device. This can trigger a crash in the tunnel transmit path. The input does not specify whether triggering it requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with netfilter flowtable and IPIP tunnels using direct transmit should check their systems; affected versions are not specified.