<?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 13:06:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43278</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43278</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-43278</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — 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://127.0.0.1:10001/vuln/certfr-2026-avi-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43278</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43278</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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm: clear cloned request bio pointer when last clone bio completes Stale rq-&amp;gt;bio values have been observed to cause double-initialization of cloned bios in request-based device-mapper targets, leading to use-after-free and double-free scenarios. One such case occurs when using dm-multipath on top of a PCIe NVMe namespace, where cloned request bios are freed during blk_complete_request(), but rq-&amp;gt;bio is left intact. Subsequent clone teardown then attempts to free the same bios again via blk_rq_unprep_clone(). The resulting double-free path looks like:   nvme_pci_complete_batch()     nvme_complete_batch()       blk_mq_end_request_batch()         blk_complete_request()        // called on a DM clone request           bio_endio()                 // first free of all clone bios           ...         rq-&amp;gt;end_io()                  // end_clone_request()           dm_complete_request(tio-&amp;gt;orig)             dm_softirq_done()               dm_done()                 dm_end_request()                   blk_rq_unprep_clone()  // second free of clone bios Fix this by clearing the clone request&amp;#39;s bio pointer when the last cloned bio completes, ensuring that later teardown paths do not attempt to free already-released bios.&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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm: clear cloned request bio pointer when last clone bio completes Stale rq-&amp;gt;bio values have been observed to cause double-initialization of cloned bios in request-based device-mapper targets, leading to use-after-free and double-free scenarios. One such case occurs when using dm-multipath on top of a PCIe NVMe namespace, where cloned request bios are freed during blk_complete_request(), but rq-&amp;gt;bio is left intact. Subsequent clone teardown then attempts to free the same bios again via blk_rq_unprep_clone(). The resulting double-free path looks like:   nvme_pci_complete_batch()     nvme_complete_batch()       blk_mq_end_request_batch()         blk_complete_request()        // called on a DM clone request           bio_endio()                 // first free of all clone bios           ...         rq-&amp;gt;end_io()                  // end_clone_request()           dm_complete_request(tio-&amp;gt;orig)             dm_softirq_done()               dm_done()                 dm_end_request()                   blk_rq_unprep_clone()  // second free of clone bios Fix this by clearing the clone request&amp;#39;s bio pointer when the last cloned bio completes, ensuring that later teardown paths do not attempt to free already-released bios.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43278</guid>
    </item>
  </channel>
</rss>
