<?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 14:27:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74702</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74702</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-74702</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — 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-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74702</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74702</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: reject feature changes after endpoint vhost_scsi_setup_vq_cmds() runs from VHOST_SCSI_SET_ENDPOINT and allocates each command&amp;#39;s protection scatterlist array (prot_sgl) according to the acknowledged VIRTIO_SCSI_F_T10_PI bit.  The command pools are not rebuilt when VHOST_SET_FEATURES changes that bit later. Although virtio feature bits must not change after feature negotiation, vhost_scsi_set_features() currently accepts such a request after the endpoint is active and updates acked_features.  Enabling T10-PI after endpoint setup therefore leaves prot_sgl NULL while the I/O path follows the new feature bit. For a 129-page protection payload, vhost_scsi_mapal() passes the missing first chunk to sg_alloc_table_chained():   sg_alloc_table_chained(table, 129, first_chunk=NULL,                          nents_first_chunk=inline_sg_cnt) sg_pool_index() then hits:   BUG_ON(nents &amp;gt; SG_CHUNK_SIZE);   /* 129 &amp;gt; 128 */ The kernel reported the following call trace and register state:   Call Trace:    &amp;lt;TASK&amp;gt;    ? __sg_alloc_table+0x1d8/0x250    ? __pfx_vhost_run_work_list+0x10/0x10 [vhost]    sg_alloc_table_chained+0x59/0xf0    ? __pfx_sg_pool_alloc+0x10/0x10    ? vhost_scsi_calc_sgls.constprop.0+0x43/0x60 [vhost_scsi]    vhost_scsi_handle_vq+0xf02/0x1700 [vhost_scsi]    ? __pfx_vhost_scsi_handle_vq+0x10/0x10 [vhost_scsi]    vhost_scsi_handle_kick+0x37/0x50 [vhost_scsi]    vhost_run_work_list+0x8e/0xd0 [vhost]…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: reject feature changes after endpoint vhost_scsi_setup_vq_cmds() runs from VHOST_SCSI_SET_ENDPOINT and allocates each command&amp;#39;s protection scatterlist array (prot_sgl) according to the acknowledged VIRTIO_SCSI_F_T10_PI bit.  The command pools are not rebuilt when VHOST_SET_FEATURES changes that bit later. Although virtio feature bits must not change after feature negotiation, vhost_scsi_set_features() currently accepts such a request after the endpoint is active and updates acked_features.  Enabling T10-PI after endpoint setup therefore leaves prot_sgl NULL while the I/O path follows the new feature bit. For a 129-page protection payload, vhost_scsi_mapal() passes the missing first chunk to sg_alloc_table_chained():   sg_alloc_table_chained(table, 129, first_chunk=NULL,                          nents_first_chunk=inline_sg_cnt) sg_pool_index() then hits:   BUG_ON(nents &amp;gt; SG_CHUNK_SIZE);   /* 129 &amp;gt; 128 */ The kernel reported the following call trace and register state:   Call Trace:    &amp;lt;TASK&amp;gt;    ? __sg_alloc_table+0x1d8/0x250    ? __pfx_vhost_run_work_list+0x10/0x10 [vhost]    sg_alloc_table_chained+0x59/0xf0    ? __pfx_sg_pool_alloc+0x10/0x10    ? vhost_scsi_calc_sgls.constprop.0+0x43/0x60 [vhost_scsi]    vhost_scsi_handle_vq+0xf02/0x1700 [vhost_scsi]    ? __pfx_vhost_scsi_handle_vq+0x10/0x10 [vhost_scsi]    vhost_scsi_handle_kick+0x37/0x50 [vhost_scsi]    vhost_run_work_list+0x8e/0xd0 [vhost]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74702</guid>
    </item>
  </channel>
</rss>
