https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:42:11 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64062 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix potential deadlock in write-through mode</p> <p>Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn&#39;t yet written to the end. Unfortunately, it can&#39;t be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes.</p> <p>Even though it has been marked dirty, premature writeback can&#39;t occur as the caller is holding both inode-&gt;i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx-&gt;wb_lock (which will cause flushing to wait and writeback to skip or wait).</p> <p>Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix potential deadlock in write-through mode</p> <p>Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn&#39;t yet written to the end. Unfortunately, it can&#39;t be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes.</p> <p>Even though it has been marked dirty, premature writeback can&#39;t occur as the caller is holding both inode-&gt;i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx-&gt;wb_lock (which will cause flushing to wait and writeback to skip or wait).</p> <p>Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.</p> https://vulnerability.circl.lu/vuln/cve-2026-64062