<?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 11:37:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26962</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26962</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-26962</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26962</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26962</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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-raid456, md/raid456: fix a deadlock for dm-raid456 while io concurrent with reshape For raid456, if reshape is still in progress, then IO across reshape position will wait for reshape to make progress. However, for dm-raid, in following cases reshape will never make progress hence IO will hang: 1) the array is read-only; 2) MD_RECOVERY_WAIT is set; 3) MD_RECOVERY_FROZEN is set; After commit c467e97f079f (&amp;#34;md/raid6: use valid sector values to determine if an I/O should wait on the reshape&amp;#34;) fix the problem that IO across reshape position doesn&amp;#39;t wait for reshape, the dm-raid test shell/lvconvert-raid-reshape.sh start to hang: [root@fedora ~]# cat /proc/979/stack [&amp;lt;0&amp;gt;] wait_woken+0x7d/0x90 [&amp;lt;0&amp;gt;] raid5_make_request+0x929/0x1d70 [raid456] [&amp;lt;0&amp;gt;] md_handle_request+0xc2/0x3b0 [md_mod] [&amp;lt;0&amp;gt;] raid_map+0x2c/0x50 [dm_raid] [&amp;lt;0&amp;gt;] __map_bio+0x251/0x380 [dm_mod] [&amp;lt;0&amp;gt;] dm_submit_bio+0x1f0/0x760 [dm_mod] [&amp;lt;0&amp;gt;] __submit_bio+0xc2/0x1c0 [&amp;lt;0&amp;gt;] submit_bio_noacct_nocheck+0x17f/0x450 [&amp;lt;0&amp;gt;] submit_bio_noacct+0x2bc/0x780 [&amp;lt;0&amp;gt;] submit_bio+0x70/0xc0 [&amp;lt;0&amp;gt;] mpage_readahead+0x169/0x1f0 [&amp;lt;0&amp;gt;] blkdev_readahead+0x18/0x30 [&amp;lt;0&amp;gt;] read_pages+0x7c/0x3b0 [&amp;lt;0&amp;gt;] page_cache_ra_unbounded+0x1ab/0x280 [&amp;lt;0&amp;gt;] force_page_cache_ra+0x9e/0x130 [&amp;lt;0&amp;gt;] page_cache_sync_ra+0x3b/0x110 [&amp;lt;0&amp;gt;] filemap_get_pages+0x143/0xa30 [&amp;lt;0&amp;gt;] filemap_read+0xdc/0x4b0 [&amp;lt;0&amp;gt;] blkdev_read_iter+0x75/0x200 [&amp;lt;0&amp;gt;] vfs_read+0x272/0x460 [&amp;lt;0&amp;gt;] ksys_read+0x7a/0x170 [&amp;lt;0&amp;gt;] __x64_sys_read+0x1c…&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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-raid456, md/raid456: fix a deadlock for dm-raid456 while io concurrent with reshape For raid456, if reshape is still in progress, then IO across reshape position will wait for reshape to make progress. However, for dm-raid, in following cases reshape will never make progress hence IO will hang: 1) the array is read-only; 2) MD_RECOVERY_WAIT is set; 3) MD_RECOVERY_FROZEN is set; After commit c467e97f079f (&amp;#34;md/raid6: use valid sector values to determine if an I/O should wait on the reshape&amp;#34;) fix the problem that IO across reshape position doesn&amp;#39;t wait for reshape, the dm-raid test shell/lvconvert-raid-reshape.sh start to hang: [root@fedora ~]# cat /proc/979/stack [&amp;lt;0&amp;gt;] wait_woken+0x7d/0x90 [&amp;lt;0&amp;gt;] raid5_make_request+0x929/0x1d70 [raid456] [&amp;lt;0&amp;gt;] md_handle_request+0xc2/0x3b0 [md_mod] [&amp;lt;0&amp;gt;] raid_map+0x2c/0x50 [dm_raid] [&amp;lt;0&amp;gt;] __map_bio+0x251/0x380 [dm_mod] [&amp;lt;0&amp;gt;] dm_submit_bio+0x1f0/0x760 [dm_mod] [&amp;lt;0&amp;gt;] __submit_bio+0xc2/0x1c0 [&amp;lt;0&amp;gt;] submit_bio_noacct_nocheck+0x17f/0x450 [&amp;lt;0&amp;gt;] submit_bio_noacct+0x2bc/0x780 [&amp;lt;0&amp;gt;] submit_bio+0x70/0xc0 [&amp;lt;0&amp;gt;] mpage_readahead+0x169/0x1f0 [&amp;lt;0&amp;gt;] blkdev_readahead+0x18/0x30 [&amp;lt;0&amp;gt;] read_pages+0x7c/0x3b0 [&amp;lt;0&amp;gt;] page_cache_ra_unbounded+0x1ab/0x280 [&amp;lt;0&amp;gt;] force_page_cache_ra+0x9e/0x130 [&amp;lt;0&amp;gt;] page_cache_sync_ra+0x3b/0x110 [&amp;lt;0&amp;gt;] filemap_get_pages+0x143/0xa30 [&amp;lt;0&amp;gt;] filemap_read+0xdc/0x4b0 [&amp;lt;0&amp;gt;] blkdev_read_iter+0x75/0x200 [&amp;lt;0&amp;gt;] vfs_read+0x272/0x460 [&amp;lt;0&amp;gt;] ksys_read+0x7a/0x170 [&amp;lt;0&amp;gt;] __x64_sys_read+0x1c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26962</guid>
    </item>
  </channel>
</rss>
