Vulnerability in Linux Kernel: 'scheduling while atomic' on aux critical err interrupt
Summary
GSD-2022-1001187: ice: fix 'scheduling while atomic' on aux critical err interrupt. Affects Kernel versions >= 348048e724a0e8f08b63948d728d27596f6d3769, < 59e88a50afad7469c55804e46bf2924b9130281f. 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 critical component of the Linux operating system, responsible for managing system resources and providing an interface between hardware and software. It is widely used across various devices and platforms. This vulnerability specifically affects the Linux Kernel version v5.14 to v5.17.1. The vulnerability arises from a 'scheduling while atomic' issue in the aux critical err interrupt of the ice driver. This vulnerability could potentially lead to system instability or crashes.
Vulnerability Detail
The vulnerability occurs due to improper handling of scheduling while in an atomic context in the aux critical err interrupt of the ice driver. This can result in a situation where the kernel scheduler attempts to schedule a task while already in an atomic context, leading to a 'scheduling while atomic' error. An attacker could potentially exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code with elevated privileges. 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
This vulnerability in the Linux Kernel, specifically in the aux critical err interrupt of the ice driver, could potentially lead to system instability or allow attackers to execute arbitrary code with elevated privileges. It is crucial to update the Linux Kernel to the latest version (v5.17.2) to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from system instability to potential privilege escalation or denial-of-service attacks.
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.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the necessary updates to mitigate any potential risks.
There are no specific prerequisites mentioned for exploiting this vulnerability. However, an attacker would require access to the affected system to exploit it.
For more details about this vulnerability, including the specific code changes and commits, you can refer to the source link provided in the database_specific section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
