net/sched: sch_ets: don't peek at classes beyond 'nbands' in Kernel
Summary
GSD-2021-1002477: net/sched: sch_ets: don't peek at classes beyond 'nbands'. Affects Kernel versions >= dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33, < ae2659d2c670252759ee9c823c4e039c0e05a6f2. 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 manages system resources and provides an interface for applications to interact with the hardware. It is responsible for tasks such as process management, memory management, and device drivers. The sch_ets module in the Kernel is used for packet scheduling in network traffic management. It implements the Enhanced Transmission Selection (ETS) algorithm, which allows for bandwidth allocation to different classes of traffic. However, a vulnerability has been discovered in the sch_ets module that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in the sch_ets module allows an attacker to access classes beyond the specified 'nbands' limit. This can result in unauthorized access to sensitive data or the execution of arbitrary code. The issue was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.10.83. 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 sch_ets module in the Kernel has a vulnerability that allows unauthorized access to classes beyond the specified limit. To mitigate this issue, it is crucial to update the Linux Kernel to version v5.10.83 or later. Regularly updating the Kernel is essential to ensure the latest security patches are applied. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to unauthorized access to sensitive data or the execution of arbitrary code.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the moment. However, it is important to apply the recommended fix to mitigate any potential risks.
The remote exploitability of this vulnerability has not been determined yet. It is advisable to update the Kernel to the latest version to ensure any potential remote attack vectors are addressed.
The main dependency for fixing this vulnerability is updating the Linux Kernel to version v5.10.83 or later. Ensure that you follow the installation instructions provided by the Kernel developers to ensure a successful update.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
