https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 05:28:10 +0000 https://vulnerability.circl.lu/vuln/cve-2022-49493 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ASoC: rt5645: Fix errorenous cleanup order</p> <p>There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &amp;rt5645-&gt;jack_detect_work and delete the &amp;rt5645-&gt;btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy.</p> <p>That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free.</p> <p>This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ASoC: rt5645: Fix errorenous cleanup order</p> <p>There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &amp;rt5645-&gt;jack_detect_work and delete the &amp;rt5645-&gt;btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy.</p> <p>That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free.</p> <p>This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync.</p> https://vulnerability.circl.lu/vuln/cve-2022-49493