<?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 12:43:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-35794</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35794</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-35794</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-35794</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35794</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 166 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-raid: really frozen sync_thread during suspend 1) commit f52f5c71f3d4 (&amp;#34;md: fix stopping sync thread&amp;#34;) remove    MD_RECOVERY_FROZEN from __md_stop_writes() and doesn&amp;#39;t realize that    dm-raid relies on __md_stop_writes() to frozen sync_thread    indirectly. Fix this problem by adding MD_RECOVERY_FROZEN in    md_stop_writes(), and since stop_sync_thread() is only used for    dm-raid in this case, also move stop_sync_thread() to    md_stop_writes(). 2) The flag MD_RECOVERY_FROZEN doesn&amp;#39;t mean that sync thread is frozen,    it only prevent new sync_thread to start, and it can&amp;#39;t stop the    running sync thread; In order to frozen sync_thread, after seting the    flag, stop_sync_thread() should be used. 3) The flag MD_RECOVERY_FROZEN doesn&amp;#39;t mean that writes are stopped, use    it as condition for md_stop_writes() in raid_postsuspend() doesn&amp;#39;t    look correct. Consider that reentrant stop_sync_thread() do nothing,    always call md_stop_writes() in raid_postsuspend(). 4) raid_message can set/clear the flag MD_RECOVERY_FROZEN at anytime,    and if MD_RECOVERY_FROZEN is cleared while the array is suspended,    new sync_thread can start unexpected. Fix this by disallow    raid_message() to change sync_thread status during suspend. Note that after commit f52f5c71f3d4 (&amp;#34;md: fix stopping sync thread&amp;#34;), the test shell/lvconvert-raid-reshape.sh start to hang in stop_sync_thread(), and with previous fixes, the test won…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 166 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-raid: really frozen sync_thread during suspend 1) commit f52f5c71f3d4 (&amp;#34;md: fix stopping sync thread&amp;#34;) remove    MD_RECOVERY_FROZEN from __md_stop_writes() and doesn&amp;#39;t realize that    dm-raid relies on __md_stop_writes() to frozen sync_thread    indirectly. Fix this problem by adding MD_RECOVERY_FROZEN in    md_stop_writes(), and since stop_sync_thread() is only used for    dm-raid in this case, also move stop_sync_thread() to    md_stop_writes(). 2) The flag MD_RECOVERY_FROZEN doesn&amp;#39;t mean that sync thread is frozen,    it only prevent new sync_thread to start, and it can&amp;#39;t stop the    running sync thread; In order to frozen sync_thread, after seting the    flag, stop_sync_thread() should be used. 3) The flag MD_RECOVERY_FROZEN doesn&amp;#39;t mean that writes are stopped, use    it as condition for md_stop_writes() in raid_postsuspend() doesn&amp;#39;t    look correct. Consider that reentrant stop_sync_thread() do nothing,    always call md_stop_writes() in raid_postsuspend(). 4) raid_message can set/clear the flag MD_RECOVERY_FROZEN at anytime,    and if MD_RECOVERY_FROZEN is cleared while the array is suspended,    new sync_thread can start unexpected. Fix this by disallow    raid_message() to change sync_thread status during suspend. Note that after commit f52f5c71f3d4 (&amp;#34;md: fix stopping sync thread&amp;#34;), the test shell/lvconvert-raid-reshape.sh start to hang in stop_sync_thread(), and with previous fixes, the test won…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35794</guid>
    </item>
  </channel>
</rss>
