net/sched: fq_pie: Out-of-Bounds Access in Traffic Path
Summary
GSD-2021-1000567: net/sched: fq_pie: fix OOB access in the traffic path. Affects Kernel versions >= ec97ecf1ebe485a17cd8395a5f35e6b80b57665a, < 7a1bdec12e43e29cc34a4394590337069d8812ce. 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 Linux Kernel is an open-source monolithic Unix-like computer operating system kernel. It provides the essential services to enable the execution of programs and manages system resources. The 'net/sched' subsystem in the Linux Kernel is responsible for network packet scheduling and traffic control. Within this subsystem, the 'fq_pie' algorithm is used for fair queuing and packet-based congestion control. However, a vulnerability has been discovered in the 'fq_pie' implementation that allows for out-of-bounds access in the traffic path.
Vulnerability Detail
The vulnerability in the 'fq_pie' algorithm arises from a lack of proper bounds checking when processing network packets. An attacker could exploit this flaw by sending specially crafted packets, leading to out-of-bounds memory access. This could result in various consequences, including system crashes, privilege escalation, or the execution of arbitrary code. The vulnerability was introduced in Linux Kernel version v5.6 and has been fixed in version v5.12.9.
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 Linux Kernel to a patched version.
Conclusion
In conclusion, the 'fq_pie' algorithm in the 'net/sched' subsystem of the Linux Kernel is vulnerable to out-of-bounds access in the traffic path. This vulnerability can have severe consequences, including system crashes and the potential for privilege escalation or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.12.9 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially lead to system crashes, privilege escalation, or the execution of arbitrary code.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you in real-time if any open-source vulnerabilities, including this one, are detected.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely by sending specially crafted packets to the target system.
The only effective mitigation is to update the Linux Kernel to a patched version. It is recommended to follow the provided fix instructions to ensure the system is protected against this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
