<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T15:52:50.809836+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64062</id>
    <title>CVE-2026-64062 — netfs: Fix potential deadlock in write-through mode</title>
    <updated>2026-10-04T15:52:50.812324+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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't yet written to the end.  Unfortunately, it can'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'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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64062"/>
  </entry>
</feed>
