<?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 04:54:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-52618</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-52618</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-2023-52618</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>OESA-2024-1566 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1566</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: core: Fix scsi_mode_sense() buffer length handling&#13;
&#13;
Several problems exist with scsi_mode_sense() buffer length handling:&#13;
&#13;
 1) The allocation length field of the MODE SENSE(10) command is 16-bits,
    occupying bytes 7 and 8 of the CDB. With this command, access to mode
    pages larger than 255 bytes is thus possible. However, the CDB
    allocation length field is set by assigning len to byte 8 only, thus
    truncating buffer length larger than 255.&#13;
&#13;
 2) If scsi_mode_sense() is called with len smaller than 8 with
    sdev-&amp;amp;gt;use_10_for_ms set, or smaller than 4 otherwise, the buffer length
    is increased to 8 and 4 respectively, and the buffer is zero filled
    with these increased values, thus corrupting the memory following the
    buffer.&#13;
&#13;
Fix these 2 problems by using put_unaligned_be16() to set the allocation
length field of MODE SENSE(10) CDB and by returning an error when len is
too small.&#13;
&#13;
Furthermore, if len is larger than 255B, always try MODE SENSE(10) first,
even if the device driver did not set sdev-&amp;amp;gt;use_10_for_ms. In case of
invalid opcode error for MODE SENSE(10), access to mode pages larger than
255 bytes are not retried using MODE SENSE(6). To avoid buffer length
overflows for the MODE_SENSE(10) case, check that len is smaller than 65535
bytes.&#13;
&#13;
While at it, also fix the folowing:&#13;
&#13;
 *…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: core: Fix scsi_mode_sense() buffer length handling&#13;
&#13;
Several problems exist with scsi_mode_sense() buffer length handling:&#13;
&#13;
 1) The allocation length field of the MODE SENSE(10) command is 16-bits,
    occupying bytes 7 and 8 of the CDB. With this command, access to mode
    pages larger than 255 bytes is thus possible. However, the CDB
    allocation length field is set by assigning len to byte 8 only, thus
    truncating buffer length larger than 255.&#13;
&#13;
 2) If scsi_mode_sense() is called with len smaller than 8 with
    sdev-&amp;amp;gt;use_10_for_ms set, or smaller than 4 otherwise, the buffer length
    is increased to 8 and 4 respectively, and the buffer is zero filled
    with these increased values, thus corrupting the memory following the
    buffer.&#13;
&#13;
Fix these 2 problems by using put_unaligned_be16() to set the allocation
length field of MODE SENSE(10) CDB and by returning an error when len is
too small.&#13;
&#13;
Furthermore, if len is larger than 255B, always try MODE SENSE(10) first,
even if the device driver did not set sdev-&amp;amp;gt;use_10_for_ms. In case of
invalid opcode error for MODE SENSE(10), access to mode pages larger than
255 bytes are not retried using MODE SENSE(6). To avoid buffer length
overflows for the MODE_SENSE(10) case, check that len is smaller than 65535
bytes.&#13;
&#13;
While at it, also fix the folowing:&#13;
&#13;
 *…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1566</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52618</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52618</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: block/rnbd-srv: Check for unlikely string overflow Since &amp;#34;dev_search_path&amp;#34; can technically be as large as PATH_MAX, there was a risk of truncation when copying it and a second string into &amp;#34;full_path&amp;#34; since it was also PATH_MAX sized. The W=1 builds were reporting this warning: drivers/block/rnbd/rnbd-srv.c: In function &amp;#39;process_msg_open.isra&amp;#39;: drivers/block/rnbd/rnbd-srv.c:616:51: warning: &amp;#39;%s&amp;#39; directive output may be truncated writing up to 254 bytes into a region of size between 0 and 4095 [-Wformat-truncation=]   616 |                 snprintf(full_path, PATH_MAX, &amp;#34;%s/%s&amp;#34;,       |                                                   ^~ In function &amp;#39;rnbd_srv_get_full_path&amp;#39;,     inlined from &amp;#39;process_msg_open.isra&amp;#39; at drivers/block/rnbd/rnbd-srv.c:721:14: drivers/block/rnbd/rnbd-srv.c:616:17: note: &amp;#39;snprintf&amp;#39; output between 2 and 4351 bytes into a destination of size 4096   616 |                 snprintf(full_path, PATH_MAX, &amp;#34;%s/%s&amp;#34;,       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   617 |                          dev_search_path, dev_name);       |                          ~~~~~~~~~~~~~~~~~~~~~~~~~~ To fix this, unconditionally check for truncation (as was already done for the case where &amp;#34;%SESSNAME%&amp;#34; was present).&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: block/rnbd-srv: Check for unlikely string overflow Since &amp;#34;dev_search_path&amp;#34; can technically be as large as PATH_MAX, there was a risk of truncation when copying it and a second string into &amp;#34;full_path&amp;#34; since it was also PATH_MAX sized. The W=1 builds were reporting this warning: drivers/block/rnbd/rnbd-srv.c: In function &amp;#39;process_msg_open.isra&amp;#39;: drivers/block/rnbd/rnbd-srv.c:616:51: warning: &amp;#39;%s&amp;#39; directive output may be truncated writing up to 254 bytes into a region of size between 0 and 4095 [-Wformat-truncation=]   616 |                 snprintf(full_path, PATH_MAX, &amp;#34;%s/%s&amp;#34;,       |                                                   ^~ In function &amp;#39;rnbd_srv_get_full_path&amp;#39;,     inlined from &amp;#39;process_msg_open.isra&amp;#39; at drivers/block/rnbd/rnbd-srv.c:721:14: drivers/block/rnbd/rnbd-srv.c:616:17: note: &amp;#39;snprintf&amp;#39; output between 2 and 4351 bytes into a destination of size 4096   616 |                 snprintf(full_path, PATH_MAX, &amp;#34;%s/%s&amp;#34;,       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   617 |                          dev_search_path, dev_name);       |                          ~~~~~~~~~~~~~~~~~~~~~~~~~~ To fix this, unconditionally check for truncation (as was already done for the case where &amp;#34;%SESSNAME%&amp;#34; was present).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52618</guid>
    </item>
  </channel>
</rss>
