fou: Don't allow 0 for FOU_ATTR_IPPROTO.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 23461551c00628c3f3fe9cf837bf53cf8f212b63 · < 9b75dff8446ec871030d8daf5a69e74f5fe8b956| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fou: Don't allow 0 for FOU_ATTR_IPPROTO.
fou_udp_recv() has the same problem mentioned in the previous patch.
If FOU_ATTR_IPPROTO is set to 0, skb is not freed by fou_udp_recv() nor "resubmit"-ted in ip_protocol_deliver_rcu().
Let's forbid 0 for FOU_ATTR_IPPROTO.
From the CVE record · Linux
The Linux kernel's FOU UDP receive path mishandles packets when FOU_ATTR_IPPROTO is set to 0: it neither frees the packet buffer nor resubmits the packet for protocol delivery. The input does not specify the resulting impact or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with FOU support should check their systems; affected versions are not specified.