net: Only allow init netns to set default tcp cong to a restricted algo
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6670e152447732ba90626f36dfc015a13fbf150e · < 8d432592f30fcc34ef5a10aac4887b4897884493| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: Only allow init netns to set default tcp cong to a restricted algo
tcp_set_default_congestion_control() is netns-safe in that it writes to &net->ipv4.tcp_congestion_control, but it also sets ca->flags |= TCP_CONG_NON_RESTRICTED which is not namespaced. This has the unintended side-effect of changing the global net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it is read-only: 97684f0970f6 ("net: Make tcp_allowed_congestion_control readonly in non-init netns")
Resolve this netns "leak" by only allowing the init netns to set the default algorithm to one that is restricted. This restriction could be removed if tcp_allowed_congestion_control were namespace-ified in the future.
This bug was uncovered with https://github.com/JonathonReinhart/linux-netns-sysctl-verify
From the CVE record · Linux
The Linux kernel lets a non-initial network namespace set a restricted default TCP congestion-control algorithm in a way that also changes a global setting. Someone able to set that namespace's default can change the global allowed-congestion-control setting despite its being read-only in non-initial namespaces. The input does not specify whether authentication or further user interaction is required.
Engineers running Linux kernels with network namespaces should check whether their kernel is affected; affected versions are not specified.