<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 02:47:39 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31703</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31703</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-31703</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0782 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0782</link>
      <description>certfr-2026-avi-0782</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0782</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31703</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31703</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 97 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like:   wb_get(new_wb);   while (1) {     list = llist_del_all(&amp;amp;new_wb-&amp;gt;switch_wbs_ctxs);     /* Nothing to do? */     if (!list)       break;     ... process the items ...   } Now adding of items to the list looks like: wb_queue_isw()   if (llist_add(&amp;amp;isw-&amp;gt;list, &amp;amp;wb-&amp;gt;switch_wbs_ctxs))     queue_work(isw_wq, &amp;amp;wb-&amp;gt;switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb-&amp;gt;switch_work is pending while wb-&amp;gt;switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -&amp;gt; no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -&amp;gt; 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let&amp;#39;s avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb-&amp;gt;switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.&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 97 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like:   wb_get(new_wb);   while (1) {     list = llist_del_all(&amp;amp;new_wb-&amp;gt;switch_wbs_ctxs);     /* Nothing to do? */     if (!list)       break;     ... process the items ...   } Now adding of items to the list looks like: wb_queue_isw()   if (llist_add(&amp;amp;isw-&amp;gt;list, &amp;amp;wb-&amp;gt;switch_wbs_ctxs))     queue_work(isw_wq, &amp;amp;wb-&amp;gt;switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb-&amp;gt;switch_work is pending while wb-&amp;gt;switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -&amp;gt; no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -&amp;gt; 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let&amp;#39;s avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb-&amp;gt;switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31703</guid>
    </item>
  </channel>
</rss>
