First published: Fri Sep 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire() If the __qcuefi pointer is not set, then in the original code, we would hold onto the lock. That means that if we tried to set it later, then it would cause a deadlock. Drop the lock on the error path. That's what all the callers are expecting.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.7<6.10.11 | |
Linux Kernel | =6.11-rc1 | |
Linux Kernel | =6.11-rc2 | |
Linux Kernel | =6.11-rc3 | |
Linux Kernel | =6.11-rc4 | |
Linux Kernel | =6.11-rc5 | |
Linux Kernel | =6.11-rc6 | |
Linux Kernel | =6.11-rc7 | |
debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-46868 has a medium severity level due to potential deadlock issues in the Linux kernel.
To fix CVE-2024-46868, update to the latest kernel versions or package releases that include the fix.
CVE-2024-46868 affects Linux kernel versions 6.7 up to 6.10.11 and 6.11 release candidates.
No, CVE-2024-46868 is not a remote vulnerability, it is related to internal locking mechanisms in the kernel.
CVE-2024-46868 impacts systems running specific versions of the Linux kernel, primarily in environments utilizing affected kernel features.