https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 08:46:43 +0000 https://vulnerability.circl.lu/vuln/cve-2023-52629 <p><strong>Affected:</strong> Linux, linux_kernel</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sh: push-switch: Reorder cleanup operations to avoid use-after-free bug</p> <p>The original code puts flush_work() before timer_shutdown_sync() in switch_drv_remove(). Although we use flush_work() to stop the worker, it could be rescheduled in switch_timer(). As a result, a use-after-free bug can occur. The details are shown below:</p> <p>(cpu 0) | (cpu 1) switch_drv_remove() | flush_work() | ... | switch_timer // timer | schedule_work(&amp;psw-&gt;work) timer_shutdown_sync() | ... | switch_work_handler // worker kfree(psw) // free | | psw-&gt;state = 0 // use</p> <p>This patch puts timer_shutdown_sync() before flush_work() to mitigate the bugs. As a result, the worker and timer will be stopped safely before the deallocate operations.</p> <p><strong>Affected:</strong> Linux, linux_kernel</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sh: push-switch: Reorder cleanup operations to avoid use-after-free bug</p> <p>The original code puts flush_work() before timer_shutdown_sync() in switch_drv_remove(). Although we use flush_work() to stop the worker, it could be rescheduled in switch_timer(). As a result, a use-after-free bug can occur. The details are shown below:</p> <p>(cpu 0) | (cpu 1) switch_drv_remove() | flush_work() | ... | switch_timer // timer | schedule_work(&amp;psw-&gt;work) timer_shutdown_sync() | ... | switch_work_handler // worker kfree(psw) // free | | psw-&gt;state = 0 // use</p> <p>This patch puts timer_shutdown_sync() before flush_work() to mitigate the bugs. As a result, the worker and timer will be stopped safely before the deallocate operations.</p> https://vulnerability.circl.lu/vuln/cve-2023-52629