Voluntarily Schedule During Key Setting in s390/gmap
Summary
GSD-2022-1003464: s390/gmap: voluntarily schedule during key setting. Affects Kernel versions < 01137d898039cd1ca44effc8f35b35e39309d078. 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 s390/gmap package is a component of the Linux Kernel, which is responsible for managing the General Purpose Register (GPR) mapping on IBM System z architecture. It provides functionality for mapping virtual addresses to physical addresses and plays a critical role in the execution of programs on the system. The vulnerability identified in this package relates to a scheduling issue during key setting.
Vulnerability Detail
The vulnerability in s390/gmap allows for voluntary scheduling during key setting operations. This means that an attacker could potentially exploit this flaw to interrupt or manipulate the key setting process, leading to unauthorized access, privilege escalation, or other security breaches. 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 s390/gmap package in the Linux Kernel is vulnerable to a scheduling issue during key setting. This vulnerability could potentially lead to unauthorized access or privilege escalation. It is recommended to update the kernel to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The s390/gmap package is a component of the Linux Kernel that manages the General Purpose Register (GPR) mapping on IBM System z architecture.
The impact of this vulnerability could include unauthorized access, privilege escalation, or other security breaches.
No, the impact and attack plausibility of this vulnerability have not been proven yet.
To fix this vulnerability, update the Linux Kernel to version v5.10.122 or later.
No specific workaround has been mentioned for this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.