https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 01:52:46 +0000 https://vulnerability.circl.lu/vuln/cve-2025-38114 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>e1000: Move cancel_work_sync to avoid deadlock</p> <p>Previously, e1000_down called cancel_work_sync for the e1000 reset task (via e1000_down_and_stop), which takes RTNL.</p> <p>As reported by users and syzbot, a deadlock is possible in the following scenario:</p> <p>CPU 0: - RTNL is held - e1000_close - e1000_down - cancel_work_sync (cancel / wait for e1000_reset_task())</p> <p>CPU 1: - process_one_work - e1000_reset_task - take RTNL</p> <p>To remedy this, avoid calling cancel_work_sync from e1000_down (e1000_reset_task does nothing if the device is down anyway). Instead, call cancel_work_sync for e1000_reset_task when the device is being removed.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>e1000: Move cancel_work_sync to avoid deadlock</p> <p>Previously, e1000_down called cancel_work_sync for the e1000 reset task (via e1000_down_and_stop), which takes RTNL.</p> <p>As reported by users and syzbot, a deadlock is possible in the following scenario:</p> <p>CPU 0: - RTNL is held - e1000_close - e1000_down - cancel_work_sync (cancel / wait for e1000_reset_task())</p> <p>CPU 1: - process_one_work - e1000_reset_task - take RTNL</p> <p>To remedy this, avoid calling cancel_work_sync from e1000_down (e1000_reset_task does nothing if the device is down anyway). Instead, call cancel_work_sync for e1000_reset_task when the device is being removed.</p> https://vulnerability.circl.lu/vuln/cve-2025-38114