<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 23:52:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64062</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64062</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-64062</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64062</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64062</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix potential deadlock in write-through mode&lt;/p&gt;
&lt;p&gt;Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.&lt;/p&gt;
&lt;p&gt;Even though it has been marked dirty, premature writeback can&amp;#39;t occur as
the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which
will cause flushing to wait and writeback to skip or wait).&lt;/p&gt;
&lt;p&gt;Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix potential deadlock in write-through mode&lt;/p&gt;
&lt;p&gt;Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.&lt;/p&gt;
&lt;p&gt;Even though it has been marked dirty, premature writeback can&amp;#39;t occur as
the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which
will cause flushing to wait and writeback to skip or wait).&lt;/p&gt;
&lt;p&gt;Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64062</guid>
    </item>
    <item>
      <title>GHSA-pw37-pjm5-88jp</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pw37-pjm5-88jp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix potential deadlock in write-through mode&lt;/p&gt;
&lt;p&gt;Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.&lt;/p&gt;
&lt;p&gt;Even though it has been marked dirty, premature writeback can&amp;#39;t occur as
the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which
will cause flushing to wait and writeback to skip or wait).&lt;/p&gt;
&lt;p&gt;Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix potential deadlock in write-through mode&lt;/p&gt;
&lt;p&gt;Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.&lt;/p&gt;
&lt;p&gt;Even though it has been marked dirty, premature writeback can&amp;#39;t occur as
the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which
will cause flushing to wait and writeback to skip or wait).&lt;/p&gt;
&lt;p&gt;Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pw37-pjm5-88jp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64062</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64062</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential deadlock in write-through mode Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes. Even though it has been marked dirty, premature writeback can&amp;#39;t occur as the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which will cause flushing to wait and writeback to skip or wait). Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential deadlock in write-through mode Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn&amp;#39;t yet written to the end.  Unfortunately, it can&amp;#39;t be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes. Even though it has been marked dirty, premature writeback can&amp;#39;t occur as the caller is holding both inode-&amp;gt;i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx-&amp;gt;wb_lock (which will cause flushing to wait and writeback to skip or wait). Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64062</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
