https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:55:58 +0000 https://db.gcve.eu/vuln/cve-2022-49995 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: avoid use-after-free after removing device</p> <p>When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback.</p> <p>Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work.</p> <p>Since this requires wb-&gt;work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb-&gt;work_lock to an irqsafe lock.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: avoid use-after-free after removing device</p> <p>When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback.</p> <p>Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work.</p> <p>Since this requires wb-&gt;work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb-&gt;work_lock to an irqsafe lock.</p> https://db.gcve.eu/vuln/cve-2022-49995