https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 01:27:57 +0000 https://vulnerability.circl.lu/vuln/cve-2024-46692 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Mark get_wq_ctx() as atomic call</p> <p>Currently get_wq_ctx() is wrongly configured as a standard call. When two SMC calls are in sleep and one SMC wakes up, it calls get_wq_ctx() to resume the corresponding sleeping thread. But if get_wq_ctx() is interrupted, goes to sleep and another SMC call is waiting to be allocated a waitq context, it leads to a deadlock.</p> <p>To avoid this get_wq_ctx() must be an atomic call and can&#39;t be a standard SMC call. Hence mark get_wq_ctx() as a fast call.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Mark get_wq_ctx() as atomic call</p> <p>Currently get_wq_ctx() is wrongly configured as a standard call. When two SMC calls are in sleep and one SMC wakes up, it calls get_wq_ctx() to resume the corresponding sleeping thread. But if get_wq_ctx() is interrupted, goes to sleep and another SMC call is waiting to be allocated a waitq context, it leads to a deadlock.</p> <p>To avoid this get_wq_ctx() must be an atomic call and can&#39;t be a standard SMC call. Hence mark get_wq_ctx() as a fast call.</p> https://vulnerability.circl.lu/vuln/cve-2024-46692