<?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 08:59:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40008</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-40008</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-2025-40008</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1010 — 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-2025-avi-1010</link>
      <description>certfr-2025-avi-1010</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1010</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40008</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40008</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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kmsan: fix out-of-bounds access to shadow memory Running sha224_kunit on a KMSAN-enabled kernel results in a crash in kmsan_internal_set_shadow_origin():     BUG: unable to handle page fault for address: ffffbc3840291000     #PF: supervisor read access in kernel mode     #PF: error_code(0x0000) - not-present page     PGD 1810067 P4D 1810067 PUD 192d067 PMD 3c17067 PTE 0     Oops: 0000 [#1] SMP NOPTI     CPU: 0 UID: 0 PID: 81 Comm: kunit_try_catch Tainted: G N  6.17.0-rc3 #10 PREEMPT(voluntary)     Tainted: [N]=TEST     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014     RIP: 0010:kmsan_internal_set_shadow_origin+0x91/0x100     [...]     Call Trace:     &amp;lt;TASK&amp;gt;     __msan_memset+0xee/0x1a0     sha224_final+0x9e/0x350     test_hash_buffer_overruns+0x46f/0x5f0     ? kmsan_get_shadow_origin_ptr+0x46/0xa0     ? __pfx_test_hash_buffer_overruns+0x10/0x10     kunit_try_run_case+0x198/0xa00 This occurs when memset() is called on a buffer that is not 4-byte aligned and extends to the end of a guard page, i.e.  the next page is unmapped. The bug is that the loop at the end of kmsan_internal_set_shadow_origin() accesses the wrong shadow memory bytes when the address is not 4-byte aligned.  Since each 4 bytes are associated with an origin, it rounds the address and size so that it can access all the origins that contain the buffer.  However, when it check…&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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kmsan: fix out-of-bounds access to shadow memory Running sha224_kunit on a KMSAN-enabled kernel results in a crash in kmsan_internal_set_shadow_origin():     BUG: unable to handle page fault for address: ffffbc3840291000     #PF: supervisor read access in kernel mode     #PF: error_code(0x0000) - not-present page     PGD 1810067 P4D 1810067 PUD 192d067 PMD 3c17067 PTE 0     Oops: 0000 [#1] SMP NOPTI     CPU: 0 UID: 0 PID: 81 Comm: kunit_try_catch Tainted: G N  6.17.0-rc3 #10 PREEMPT(voluntary)     Tainted: [N]=TEST     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014     RIP: 0010:kmsan_internal_set_shadow_origin+0x91/0x100     [...]     Call Trace:     &amp;lt;TASK&amp;gt;     __msan_memset+0xee/0x1a0     sha224_final+0x9e/0x350     test_hash_buffer_overruns+0x46f/0x5f0     ? kmsan_get_shadow_origin_ptr+0x46/0xa0     ? __pfx_test_hash_buffer_overruns+0x10/0x10     kunit_try_run_case+0x198/0xa00 This occurs when memset() is called on a buffer that is not 4-byte aligned and extends to the end of a guard page, i.e.  the next page is unmapped. The bug is that the loop at the end of kmsan_internal_set_shadow_origin() accesses the wrong shadow memory bytes when the address is not 4-byte aligned.  Since each 4 bytes are associated with an origin, it rounds the address and size so that it can access all the origins that contain the buffer.  However, when it check…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40008</guid>
    </item>
  </channel>
</rss>
