Double Free of cond_list in selinux Package
Summary
GSD-2022-1000214: selinux: fix double free of cond_list on error paths. Affects Kernel versions < f446089a268c8fc6908488e991d28a9b936293db. 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 selinux package is a security module for the Linux kernel that provides access control security policies. It enforces mandatory access control policies that restrict user and process access to resources based on defined rules. The package is an integral part of the Linux kernel and is responsible for enforcing security policies related to SELinux (Security-Enhanced Linux).
Vulnerability Detail
The vulnerability in the selinux package involves a double free of the cond_list variable on error paths. This vulnerability can be exploited by an attacker to cause a denial-of-service condition or potentially execute arbitrary code. The double free occurs when certain error conditions are encountered during the execution of the package, leading to the freeing of the same memory location multiple times. This can result in memory corruption and potentially allow an attacker to gain unauthorized access or disrupt the system's normal operation.
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 available for this vulnerability. The recommended approach is to update the Linux kernel to the fixed version.
Conclusion
The double free vulnerability in the selinux package can have serious security implications, potentially leading to a denial-of-service condition or arbitrary code execution. It is crucial to update the Linux kernel to the fixed version to mitigate this vulnerability and ensure the system's security. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a denial-of-service condition or allow an attacker to execute arbitrary code. It can also result in memory corruption, which may lead to unauthorized access or disruption of the system's normal operation.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the recommended fix to ensure the system is protected against potential exploitation.
No, the recommended approach is to update the Linux kernel to the fixed version. There is no specific workaround available for this vulnerability.
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 vulnerability ID, affected package, fix version, and references for further information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
