<?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 00:06:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-40943</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-40943</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-40943</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2024-1894 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1894</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;
lib/generic-radix-tree.c: Don&amp;amp;apos;t overflow in peek()&#13;
&#13;
When we started spreading new inode numbers throughout most of the 64
bit inode space, that triggered some corner case bugs, in particular
some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: ufs: Fix a deadlock in the error handler&#13;
&#13;
The following deadlock has been observed on a test setup:&#13;
&#13;
 - All tags allocated&#13;
&#13;
 - The SCSI error handler calls ufshcd_eh_host_reset_handler()&#13;
&#13;
 - ufshcd_eh_host_reset_handler() queues work that calls
   ufshcd_err_handler()&#13;
&#13;
 - ufshcd_err_handler() locks up as follows:&#13;
&#13;
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt
Call trace:
 __switch_to+0x298/0x5d8
 __schedule+0x6cc/0xa94
 schedule+0x12c/0x298
 blk_mq_get_tag+0x210/0x480
 __blk_mq_alloc_request+0x1c8/0x284
 blk_get_request+0x74/0x134
 ufshcd_exec_dev_cmd+0x68/0x640
 ufshcd_verify_dev_init+0x68/0x35c
 ufshcd_probe_hba+0x12c/0x1cb8
 ufshcd_host_reset_and_restore+0x88/0x254
 ufshcd_reset_and_restore+0xd0/0x354
 ufshcd_err_handler+0x408/0xc58
 process_one_work+0x24c/0x66c
 worker_thread+0x3e8/0xa4c
 kthread+0x150/0x1b4
 ret_from_fork+0x10/0x30&#13;
&#13;
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved
request.(CVE-2021-47622)&#13;
&#13;
In the Linux kernel, the following…&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;
lib/generic-radix-tree.c: Don&amp;amp;apos;t overflow in peek()&#13;
&#13;
When we started spreading new inode numbers throughout most of the 64
bit inode space, that triggered some corner case bugs, in particular
some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: ufs: Fix a deadlock in the error handler&#13;
&#13;
The following deadlock has been observed on a test setup:&#13;
&#13;
 - All tags allocated&#13;
&#13;
 - The SCSI error handler calls ufshcd_eh_host_reset_handler()&#13;
&#13;
 - ufshcd_eh_host_reset_handler() queues work that calls
   ufshcd_err_handler()&#13;
&#13;
 - ufshcd_err_handler() locks up as follows:&#13;
&#13;
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt
Call trace:
 __switch_to+0x298/0x5d8
 __schedule+0x6cc/0xa94
 schedule+0x12c/0x298
 blk_mq_get_tag+0x210/0x480
 __blk_mq_alloc_request+0x1c8/0x284
 blk_get_request+0x74/0x134
 ufshcd_exec_dev_cmd+0x68/0x640
 ufshcd_verify_dev_init+0x68/0x35c
 ufshcd_probe_hba+0x12c/0x1cb8
 ufshcd_host_reset_and_restore+0x88/0x254
 ufshcd_reset_and_restore+0xd0/0x354
 ufshcd_err_handler+0x408/0xc58
 process_one_work+0x24c/0x66c
 worker_thread+0x3e8/0xa4c
 kthread+0x150/0x1b4
 ret_from_fork+0x10/0x30&#13;
&#13;
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved
request.(CVE-2021-47622)&#13;
&#13;
In the Linux kernel, the following…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1894</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40943</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40943</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix races between hole punching and AIO+DIO After commit &amp;#34;ocfs2: return real error code in ocfs2_dio_wr_get_block&amp;#34;, fstests/generic/300 become from always failed to sometimes failed: ======================================================================== [  473.293420 ] run fstests generic/300 [  475.296983 ] JBD2: Ignoring recovery information on journal [  475.302473 ] ocfs2: Mounting device (253,1) on (node local, slot 0) with ordered data mode. [  494.290998 ] OCFS2: ERROR (device dm-1): ocfs2_change_extent_flag: Owner 5668 has an extent at cpos 78723 which can no longer be found [  494.291609 ] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [  494.292018 ] OCFS2: File system is now read-only. [  494.292224 ] (kworker/19:11,2628,19):ocfs2_mark_extent_written:5272 ERROR: status = -30 [  494.292602 ] (kworker/19:11,2628,19):ocfs2_dio_end_io_write:2374 ERROR: status = -3 fio: io_u error on file /mnt/scratch/racer: Read-only file system: write offset=460849152, buflen=131072 ========================================================================= In __blockdev_direct_IO, ocfs2_dio_wr_get_block is called to add unwritten extents to a list.  extents are also inserted into extent tree in ocfs2_write_begin_nolock.  Then another thread call fallocate to puch a hole at one of the unwritten extent.  The extent at cpos was removed by ocfs2_remove_extent().  At end io…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix races between hole punching and AIO+DIO After commit &amp;#34;ocfs2: return real error code in ocfs2_dio_wr_get_block&amp;#34;, fstests/generic/300 become from always failed to sometimes failed: ======================================================================== [  473.293420 ] run fstests generic/300 [  475.296983 ] JBD2: Ignoring recovery information on journal [  475.302473 ] ocfs2: Mounting device (253,1) on (node local, slot 0) with ordered data mode. [  494.290998 ] OCFS2: ERROR (device dm-1): ocfs2_change_extent_flag: Owner 5668 has an extent at cpos 78723 which can no longer be found [  494.291609 ] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [  494.292018 ] OCFS2: File system is now read-only. [  494.292224 ] (kworker/19:11,2628,19):ocfs2_mark_extent_written:5272 ERROR: status = -30 [  494.292602 ] (kworker/19:11,2628,19):ocfs2_dio_end_io_write:2374 ERROR: status = -3 fio: io_u error on file /mnt/scratch/racer: Read-only file system: write offset=460849152, buflen=131072 ========================================================================= In __blockdev_direct_IO, ocfs2_dio_wr_get_block is called to add unwritten extents to a list.  extents are also inserted into extent tree in ocfs2_write_begin_nolock.  Then another thread call fallocate to puch a hole at one of the unwritten extent.  The extent at cpos was removed by ocfs2_remove_extent().  At end io…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40943</guid>
    </item>
  </channel>
</rss>
