amt: Don't support cross-netns setup.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b9022b53adad88fd6cf2b9718c9e498504f3e1dd · < e99ecc3046ea5f5c6b5e1f8b4ef854c6c6998e06| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
amt: Don't support cross-netns setup.
When a lower device is unregistered, amt_device_event() tries to unregister its upper AMT device, but it has two problems.
1. amt_lookup_upper_dev() looks up an upper device in the lower device's netns only
2. amt_device_event() unregisters a single upper device only
If AMT device is created on a lower device in another netns, removing the lower device triggers the splat below and gets stuck until all upper devices are removed. [0]
The cross-netns setup seems unintentional considering 1. and the following points:
* amt_link_setup() sets dev->netns_immutable to true * skb_scrub_packet() is not called in the fast path * iproute2 binary fails to find cross-netns lower device via link-netns: # ip -n ns1 link add amt0 link-netns ns2 type amt dev veth1 Cannot find device "veth1"
From the CVE record · Linux
The Linux kernel's AMT networking code allows an AMT device to use a lower device in another network namespace, but cannot reliably find that AMT device when the lower device is removed. A local actor able to configure and remove these network devices can trigger a warning and leave device removal stuck until the upper devices are removed.
Engineers running Linux kernels with AMT networking should check their deployments; affected versions are not specified.