net: Only allow init netns to set default tcp cong to a restricted algo in Kernel
Summary
UVI-2021-1000451: net: Only allow init netns to set default tcp cong to a restricted algo. Affects Kernel versions >= 6670e152447732ba90626f36dfc015a13fbf150e, < 992de06308d9a9584d59b96d294ac676f924e437. 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 acts as an interface between hardware and software. It manages system resources, facilitates communication between processes, and handles various tasks such as memory management, device drivers, and network protocols. The vulnerability in question pertains to the default TCP congestion control algorithm in the Kernel's networking subsystem.
Vulnerability Detail
The vulnerability allows only the initial network namespace (netns) to set the default TCP congestion control algorithm to a restricted option. This restriction ensures that only trusted processes can modify the default algorithm, preventing potential security risks. The impact and plausibility of attacks associated with this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v4.15 by commit 6670e152447732ba90626f36dfc015a13fbf150e and has been fixed in version v4.19.191 by commit 992de06308d9a9584d59b96d294ac676f924e437.
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's networking subsystem allows only the initial network namespace to set the default TCP congestion control algorithm to a restricted option. While the impact and attack plausibility have not been proven, it is recommended to update the Linux Kernel to version v4.19.191 or later to mitigate potential security risks. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown as no proven attacks have been reported. However, restricting the ability to modify the default TCP congestion control algorithm helps mitigate potential security risks.
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 in real-time to identify any open-source vulnerabilities, including this one.
Yes, a patch has been released in Linux Kernel version v4.19.191. It is recommended to update to this version or a later one to fix the vulnerability.
No, this vulnerability restricts the ability to modify the default TCP congestion control algorithm to only the initial network namespace (netns). This limitation helps prevent potential security risks.
You can refer to the vulnerability details in the Open Source Vulnerability format provided by the Cloud Security Alliance's GSD Database. The details include the commit IDs, affected versions, and relevant references.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
