<?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 05:20:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-38636</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-38636</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-2024-38636</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0632 — 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-2024-avi-0632</link>
      <description>certfr-2024-avi-0632</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0632</guid>
    </item>
    <item>
      <title>OESA-2024-1766 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1766</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer&#13;
&#13;
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the
maximum transfer length and the size of the transfer buffer. As such, it
does not account for the 4 bytes of header that prepends the SPI data
frame. This can result in out-of-bounds accesses and was confirmed with
KASAN.&#13;
&#13;
Introduce SPI_HDRSIZE to account for the header and use to allocate the
transfer buffer.(CVE-2024-36477)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: fix out-of-bounds access in ops_init&#13;
&#13;
net_alloc_generic is called by net_alloc, which is called without any
locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It
is read twice, first to allocate an array, then to set s.len, which is
later used to limit the bounds of the array access.&#13;
&#13;
It is possible that the array is allocated and another thread is
registering a new pernet ops, increments max_gen_ptrs, which is then used
to set s.len with a larger than allocated length for the variable array.&#13;
&#13;
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If
max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gpiolib: cdev: fix uninitialised kfif…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer&#13;
&#13;
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the
maximum transfer length and the size of the transfer buffer. As such, it
does not account for the 4 bytes of header that prepends the SPI data
frame. This can result in out-of-bounds accesses and was confirmed with
KASAN.&#13;
&#13;
Introduce SPI_HDRSIZE to account for the header and use to allocate the
transfer buffer.(CVE-2024-36477)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: fix out-of-bounds access in ops_init&#13;
&#13;
net_alloc_generic is called by net_alloc, which is called without any
locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It
is read twice, first to allocate an array, then to set s.len, which is
later used to limit the bounds of the array access.&#13;
&#13;
It is possible that the array is allocated and another thread is
registering a new pernet ops, increments max_gen_ptrs, which is then used
to set s.len with a larger than allocated length for the variable array.&#13;
&#13;
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If
max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gpiolib: cdev: fix uninitialised kfif…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1766</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-38636</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38636</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to recognize valid zero block address As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below: ./check zbd/010 zbd/010 (test gap zone support with F2FS)                    [failed]     runtime    ...  3.752s     something found in dmesg:     [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13     [ 4378.192349] null_blk: module loaded     [ 4378.209860] null_blk: disk nullb0 created     [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1)     [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520]                      dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0     [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug       0191 PQ: 0 ANSI: 7     [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred     [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20     [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device     ...     (See &amp;#39;/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg&amp;#39; WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace:  &amp;lt;TASK&amp;gt;  __iomap_dio_rw+0x1df/0x830  f2fs_file_read_iter+0x156/0x3d0 [f2fs]  aio_read+0x138/0x210  io_submit_one+0x188/0x8c0…&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to recognize valid zero block address As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below: ./check zbd/010 zbd/010 (test gap zone support with F2FS)                    [failed]     runtime    ...  3.752s     something found in dmesg:     [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13     [ 4378.192349] null_blk: module loaded     [ 4378.209860] null_blk: disk nullb0 created     [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1)     [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520]                      dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0     [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug       0191 PQ: 0 ANSI: 7     [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred     [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20     [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device     ...     (See &amp;#39;/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg&amp;#39; WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace:  &amp;lt;TASK&amp;gt;  __iomap_dio_rw+0x1df/0x830  f2fs_file_read_iter+0x156/0x3d0 [f2fs]  aio_read+0x138/0x210  io_submit_one+0x188/0x8c0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38636</guid>
    </item>
  </channel>
</rss>
