gue: Fix skb memleak with inner IP protocol 0.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 37dd0247797b168ad1cc7f5dbec825a1ee66535b · < 5437a279804ced8088cabb945dba88a26d828f8c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gue: Fix skb memleak with inner IP protocol 0.
syzbot reported skb memleak below. [0]
The repro generated a GUE packet with its inner protocol 0.
gue_udp_recv() returns -guehdr->proto_ctype for "resubmit" in ip_protocol_deliver_rcu(), but this only works with non-zero protocol number.
Let's drop such packets.
Note that 0 is a valid number (IPv6 Hop-by-Hop Option).
I think it is not practical to encap HOPOPT in GUE, so once someone starts to complain, we could pass down a resubmit flag pointer to distinguish two zeros from the upper layer:
From the CVE record · Linux
The Linux kernel's GUE receive path can leak packet memory when it processes a GUE packet with inner protocol 0. An attacker who can deliver such packets to a system processing GUE traffic could cause a memory leak; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels that process GUE traffic should check whether their kernel includes the fix; affected versions are not specified.