<?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:51:02 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26983</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26983</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-26983</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</link>
      <description>certfr-2024-avi-0381</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26983</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26983</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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bootconfig: use memblock_free_late to free xbc memory to buddy On the time to free xbc memory in xbc_exit(), memblock may has handed over memory to buddy allocator. So it doesn&amp;#39;t make sense to free memory back to memblock. memblock_free() called by xbc_exit() even causes UAF bugs on architectures with CONFIG_ARCH_KEEP_MEMBLOCK disabled like x86. Following KASAN logs shows this case. This patch fixes the xbc memory free problem by calling memblock_free() in early xbc init error rewind path and calling memblock_free_late() in xbc exit path to free memory to buddy allocator. [    9.410890] ================================================================== [    9.418962] BUG: KASAN: use-after-free in memblock_isolate_range+0x12d/0x260 [    9.426850] Read of size 8 at addr ffff88845dd30000 by task swapper/0/1 [    9.435901] CPU: 9 PID: 1 Comm: swapper/0 Tainted: G     U 6.9.0-rc3-00208-g586b5dfb51b9 #5 [    9.446403] Hardware name: Intel Corporation RPLP LP5 (CPU:RaptorLake)/RPLP LP5 (ID:13), BIOS IRPPN02.01.01.00.00.19.015.D-00000000 Dec 28 2023 [    9.460789] Call Trace: [    9.463518]  &amp;lt;TASK&amp;gt; [    9.465859]  dump_stack_lvl+0x53/0x70 [    9.469949]  print_report+0xce/0x610 [    9.473944]  ? __virt_addr_valid+0xf5/0x1b0 [    9.478619]  ? memblock_isolate_range+0x12d/0x260 [    9.483877]  kasan_report+0xc6/0x100 [    9.487870]  ? memblock_isolate_range+0x12d/0x260 [    9.493125]  memblock_isolate_range+0x12d/0x26…&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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bootconfig: use memblock_free_late to free xbc memory to buddy On the time to free xbc memory in xbc_exit(), memblock may has handed over memory to buddy allocator. So it doesn&amp;#39;t make sense to free memory back to memblock. memblock_free() called by xbc_exit() even causes UAF bugs on architectures with CONFIG_ARCH_KEEP_MEMBLOCK disabled like x86. Following KASAN logs shows this case. This patch fixes the xbc memory free problem by calling memblock_free() in early xbc init error rewind path and calling memblock_free_late() in xbc exit path to free memory to buddy allocator. [    9.410890] ================================================================== [    9.418962] BUG: KASAN: use-after-free in memblock_isolate_range+0x12d/0x260 [    9.426850] Read of size 8 at addr ffff88845dd30000 by task swapper/0/1 [    9.435901] CPU: 9 PID: 1 Comm: swapper/0 Tainted: G     U 6.9.0-rc3-00208-g586b5dfb51b9 #5 [    9.446403] Hardware name: Intel Corporation RPLP LP5 (CPU:RaptorLake)/RPLP LP5 (ID:13), BIOS IRPPN02.01.01.00.00.19.015.D-00000000 Dec 28 2023 [    9.460789] Call Trace: [    9.463518]  &amp;lt;TASK&amp;gt; [    9.465859]  dump_stack_lvl+0x53/0x70 [    9.469949]  print_report+0xce/0x610 [    9.473944]  ? __virt_addr_valid+0xf5/0x1b0 [    9.478619]  ? memblock_isolate_range+0x12d/0x260 [    9.483877]  kasan_report+0xc6/0x100 [    9.487870]  ? memblock_isolate_range+0x12d/0x260 [    9.493125]  memblock_isolate_range+0x12d/0x26…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26983</guid>
    </item>
  </channel>
</rss>
