Vulnerability in Kernel: net: Make tcp_allowed_congestion_control readonly in non-init netns
Summary
GSD-2021-1000017: net: Make tcp_allowed_congestion_control readonly in non-init netns. Affects Kernel versions >= 9cb8e048e5d93825ec5e8dfb5b8df4987ea25745, < 1ccdf1bed140820240e383ba0accc474ffc7f006. 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
Background
The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and enables the execution of applications. The tcp_allowed_congestion_control variable in the Kernel controls the allowed congestion control algorithms for TCP connections. In non-init netns, this variable was not set as read-only, potentially allowing unauthorized modification of congestion control settings.
Vulnerability Detail
The vulnerability arises from the tcp_allowed_congestion_control variable not being set as read-only in non-init netns. An attacker with sufficient privileges in a non-init network namespace could modify the congestion control settings for TCP connections, potentially leading to performance degradation, network instability, or even denial of service. The impact and attack plausibility of this vulnerability have not been proven yet.
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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel, specifically related to the tcp_allowed_congestion_control variable in non-init netns, could potentially lead to performance degradation, network instability, or denial of service. It is crucial to update the Kernel to the latest version (v5.11.16 or later) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could include performance degradation, network instability, or denial of service if exploited by an attacker with sufficient privileges.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
Yes, the vulnerability has been fixed in Linux Kernel version v5.11.16. Users should update their Kernel to the latest version to mitigate the risk.
The exact attack vector and exploitability of this vulnerability have not been proven yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.
You can find more information about this vulnerability in the GSD-2021-1000017 entry of the GSD Database maintained by the Cloud Security Alliance. The link to the specific vulnerability entry is provided in the references section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
