Vulnerability in Kernel Package: tcp_mtup_probe_success vs wrong snd_cwnd
Summary
GSD-2022-1003957: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd. Affects Kernel versions >= 5d424d5a674f782d0659a3b66d951f412901faee, < 42726877453afdbe1508a8a96884ea907741d9a7. 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 package is a fundamental component of the Linux operating system, responsible for managing the system's core functions. It provides an interface between the hardware and software layers, enabling communication and coordination between various system components. This vulnerability specifically affects the tcp_mtup_probe_success function within the Kernel package.
Vulnerability Detail
The tcp_mtup_probe_success function in the Kernel package is susceptible to a flaw that results in an incorrect value being assigned to the snd_cwnd variable. This vulnerability was introduced in version v2.6.17 of the Kernel package and has been present until version v4.14.283. An attacker could potentially exploit this vulnerability to manipulate the congestion window size, leading to various adverse effects such as network congestion, performance degradation, or even denial of service.
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. It is essential to apply the fix by updating the Kernel package to the recommended version.
Conclusion
The vulnerability in the Kernel package's tcp_mtup_probe_success function can have significant implications for network performance and stability. It is crucial to update the Kernel package to version v4.14.283 or later to address this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to network congestion, performance degradation, or denial of service, depending on how it is exploited.
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 to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.
No, only versions from v2.6.17 to v4.14.283 of the Kernel package are affected by this vulnerability. Updating to version v4.14.283 or later resolves the issue.
No, updating the Kernel package to the recommended version is the only known solution to mitigate this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
