<?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:14:12 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:10854 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2025:10854</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: exfat: fix random stack corruption after get_block (CVE-2025-22036)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: exfat: fix random stack corruption after get_block (CVE-2025-22036)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2025:10854</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-22036</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-22036</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-22036</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0449 — 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-2025-avi-0449</link>
      <description>certfr-2025-avi-0449</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0449</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22036</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22036</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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exfat: fix random stack corruption after get_block When get_block is called with a buffer_head allocated on the stack, such as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the following race condition situation.      &amp;lt;CPU 0&amp;gt;                      &amp;lt;CPU 1&amp;gt; mpage_read_folio   &amp;lt;&amp;lt;bh on stack&amp;gt;&amp;gt;   do_mpage_readpage     exfat_get_block       bh_read         __bh_read 	  get_bh(bh)           submit_bh           wait_on_buffer                               ...                               end_buffer_read_sync                                 __end_buffer_read_notouch                                    unlock_buffer           &amp;lt;&amp;lt;keep going&amp;gt;&amp;gt;         ...       ...     ...   ... &amp;lt;&amp;lt;bh is not valid out of mpage_read_folio&amp;gt;&amp;gt;    .    . another_function   &amp;lt;&amp;lt;variable A on stack&amp;gt;&amp;gt;                                    put_bh(bh)                                      atomic_dec(bh-&amp;gt;b_count)   * stack corruption here * This patch returns -EAGAIN if a folio does not have buffers when bh_read needs to be called. By doing this, the caller can fallback to functions like block_read_full_folio(), create a buffer_head in the folio, and then call get_block again. Let&amp;#39;s do not call bh_read() with on-stack buffer_head.&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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exfat: fix random stack corruption after get_block When get_block is called with a buffer_head allocated on the stack, such as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the following race condition situation.      &amp;lt;CPU 0&amp;gt;                      &amp;lt;CPU 1&amp;gt; mpage_read_folio   &amp;lt;&amp;lt;bh on stack&amp;gt;&amp;gt;   do_mpage_readpage     exfat_get_block       bh_read         __bh_read 	  get_bh(bh)           submit_bh           wait_on_buffer                               ...                               end_buffer_read_sync                                 __end_buffer_read_notouch                                    unlock_buffer           &amp;lt;&amp;lt;keep going&amp;gt;&amp;gt;         ...       ...     ...   ... &amp;lt;&amp;lt;bh is not valid out of mpage_read_folio&amp;gt;&amp;gt;    .    . another_function   &amp;lt;&amp;lt;variable A on stack&amp;gt;&amp;gt;                                    put_bh(bh)                                      atomic_dec(bh-&amp;gt;b_count)   * stack corruption here * This patch returns -EAGAIN if a folio does not have buffers when bh_read needs to be called. By doing this, the caller can fallback to functions like block_read_full_folio(), create a buffer_head in the folio, and then call get_block again. Let&amp;#39;s do not call bh_read() with on-stack buffer_head.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22036</guid>
    </item>
  </channel>
</rss>
