Double Free of GS and RI CBs on fork() Failure in Linux Kernel
Summary
GSD-2022-1005435: s390: fix double free of GS and RI CBs on fork() failure. Affects Kernel versions >= 8d9047f8b967ce6181fd824ae922978e1b055cc0, < 8195e065abf3df84eb0ad2987e76a40f21d1791c. 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 a widely used open-source operating system kernel that serves as the foundation for various Linux distributions. It provides essential functionality for managing system resources, including process management, memory management, and device drivers. The s390 architecture is one of the supported architectures in the Linux Kernel. The vulnerability described here specifically affects the s390 architecture and involves a double free of GS (General Segment) and RI (Region Information) control blocks when a fork() system call fails.
Vulnerability Detail
The vulnerability occurs when a fork() system call fails on the s390 architecture. In this scenario, the Linux Kernel attempts to free the GS and RI control blocks twice, leading to a double free vulnerability. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v4.15 and has been fixed in version v5.15.64.
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
No specific workaround has been provided for this vulnerability.
Conclusion
The double free vulnerability in the Linux Kernel's s390 architecture, specifically related to GS and RI control blocks on fork() failure, has been addressed in version v5.15.64. Users are advised to update their Linux Kernel to this version or later to ensure the security and stability of their systems. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.
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 monitoring and 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 important to promptly update the Linux Kernel to the fixed version to mitigate any potential risks.
No, only Linux Kernel versions from v4.15 to v5.15.63 are affected by this vulnerability. The issue has been fixed in version v5.15.64.
No, the recommended approach to mitigate this vulnerability is to update the Linux Kernel to the fixed version. Applying patches or workarounds specific to this vulnerability is not available.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
