gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl().
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 86f73d4ab2f27deeff22ba9336ad103d94f12ac7 · < ff81b14010362f6188ca26fec22ff05e4da45595| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl().
Brad Spengler reported the list_del() corruption splat in gtp_net_exit_batch_rtnl(). [0]
Commit eb28fd76c0a0 ("gtp: Destroy device along with udp socket's netns dismantle.") added the for_each_netdev() loop in gtp_net_exit_batch_rtnl() to destroy devices in each netns as done in geneve and ip tunnels.
However, this could trigger ->dellink() twice for the same device during ->exit_batch_rtnl().
Say we have two netns A & B and gtp device B that resides in netns B but whose UDP socket is in netns A.
1. cleanup_net() processes netns A and then B.
2. gtp_net_exit_batch_rtnl() finds the device B while iterating netns A's gn->gtp_dev_list and calls ->dellink().
From the CVE record · Linux
The Linux kernel's GTP cleanup can call device deletion twice when a GTP device and its UDP socket are in different network namespaces. With CONFIG_DEBUG_LIST enabled, this can trigger a list-corruption check and a kernel BUG. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with GTP support should check their kernel versions; affected versions are not specified in the input.