net/sched: act_ct: fix wild memory access when clearing fragments
Summary
GSD-2021-1000228: net/sched: act_ct: fix wild memory access when clearing fragments. Affects Kernel versions >= ae372cb1750f6c95370f92fe5f5620e0954663ba, < 0648941f4c8bbf8b4b6c0b270889ae7aa769b921. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for software to interact with the hardware. The act_ct module in the net/sched subsystem is used for connection tracking. It keeps track of network connections and performs actions based on the connection state. This vulnerability specifically impacts the act_ct module when clearing fragments.
Vulnerability Detail
The vulnerability in the act_ct module of the Kernel allows for wild memory access when clearing fragments. This can potentially lead to memory corruption or unauthorized access to sensitive information. The issue was introduced in version v5.8 of the Linux Kernel and was fixed in version v5.12.4. The vulnerability arises from improper handling of fragments, which can result in accessing memory beyond the intended boundaries. An attacker could potentially exploit this vulnerability to execute arbitrary code or crash the system.
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 act_ct module of the Kernel can result in wild memory access when clearing fragments, potentially leading to memory corruption or unauthorized access to sensitive information. It is recommended to update the Linux Kernel to version v5.12.4 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption or unauthorized access to sensitive information. It may allow an attacker to execute arbitrary code or crash the system.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for open-source vulnerabilities in real-time.
Yes, the vulnerability has been fixed in Linux Kernel version v5.12.4. It is recommended to update to this version or a later one to mitigate the issue.
The exact attack vector and exploitability of this vulnerability have not been proven. However, if successfully exploited, it could potentially be triggered remotely.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
