net: Make tcp_allowed_congestion_control readonly in non-init netns
Summary
GSD-2021-1000035: net: Make tcp_allowed_congestion_control readonly in non-init netns. Affects Kernel versions >= 9cb8e048e5d93825ec5e8dfb5b8df4987ea25745, < 35d7491e2f77ce480097cabcaf93ed409e916e12. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Linux Kernel is an open-source monolithic Unix-like computer operating system kernel. It provides the essential services to allow multiple processes to run concurrently on a computer. The tcp_allowed_congestion_control variable is a global variable in the Linux Kernel that determines the allowed congestion control algorithms for TCP connections. In non-init netns (network namespaces), this variable should be read-only to prevent unauthorized modifications.
Vulnerability Detail
The vulnerability in the Linux Kernel allows unauthorized modifications to the tcp_allowed_congestion_control variable in non-init netns. An attacker with sufficient privileges in a non-init netns can modify this variable, potentially leading to the use of unauthorized or malicious congestion control algorithms for TCP connections. This could result in network performance degradation, denial of service, or other security issues.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability.
Conclusion
The vulnerability in the Linux Kernel that allows unauthorized modifications to the tcp_allowed_congestion_control variable in non-init netns can have serious consequences for network performance and security. It is crucial to update the Linux Kernel to the fixed version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's intentions and the modifications made to the tcp_allowed_congestion_control variable. Possible consequences include network performance degradation, denial of service, or other security issues.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
No, this vulnerability requires an attacker to have sufficient privileges in a non-init netns. It cannot be exploited remotely.
There are no known instances of this vulnerability being exploited in the wild.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
