Vulnerability in Linux Kernel: 'scheduling while atomic' on aux critical err interrupt
Summary
GSD-2022-1001506: ice: fix 'scheduling while atomic' on aux critical err interrupt. Affects Kernel versions >= 348048e724a0e8f08b63948d728d27596f6d3769, < 24d7ac8426306ae7ccea7f7dd612a7368fe7201d. 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 in various devices, including servers, desktops, and embedded systems. The vulnerability in question affects the Linux Kernel and specifically relates to the handling of the auxiliary critical error interrupt. This interrupt is used to signal critical errors that require immediate attention. However, a flaw in the implementation of this interrupt can lead to a 'scheduling while atomic' issue, which can cause system instability and potential security risks.
Vulnerability Detail
The vulnerability arises from a 'scheduling while atomic' problem in the Linux Kernel's handling of the auxiliary critical error interrupt. When this interrupt occurs, the kernel is in an atomic context, meaning that it cannot be preempted or rescheduled. However, due to a coding error, certain operations that are not allowed in an atomic context are performed, leading to the 'scheduling while atomic' issue. This can result in system crashes, data corruption, or even potential privilege escalation attacks. The vulnerability was introduced in Linux Kernel version v5.14 and has been fixed in version v5.16.19.
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
If updating the Linux Kernel is not immediately feasible, a possible workaround is to disable the auxiliary critical error interrupt. This can be achieved by modifying the kernel configuration or boot parameters to exclude the interrupt handler. However, it is important to note that disabling this interrupt may prevent the detection and handling of critical errors, potentially leading to system instability or data loss. Therefore, this workaround should only be considered as a temporary measure until the kernel can be updated.
Conclusion
In conclusion, the vulnerability in the Linux Kernel's handling of the auxiliary critical error interrupt can lead to system instability and potential security risks. It is crucial to update the kernel to the fixed version (v5.16.19 or later) to mitigate these risks. If immediate updating is not possible, disabling the interrupt can serve as a temporary workaround, although it may result in the loss of critical error detection and handling functionality. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in system crashes, data corruption, or potential privilege escalation attacks.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any 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 apply the fix as soon as possible to mitigate any potential risks.
A possible workaround is to disable the auxiliary critical error interrupt, but this may result in the loss of critical error detection and handling functionality. It is recommended to update the kernel to the fixed version as soon as possible.
You can refer to the Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) for more information about the fix. The vulnerability details can be found in the GSD-2022-1001506.json file in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001506.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
