<?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 09:56:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-47694</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-47694</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-2024-47694</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47694</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47694</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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix UMR pd cleanup on error flow of driver init The cited commit moves the pd allocation from function mlx5r_umr_resource_cleanup() to a new function mlx5r_umr_cleanup(). So the fix in commit [1] is broken. In error flow, will hit panic [2]. Fix it by checking pd pointer to avoid panic if it is NULL; [1] RDMA/mlx5: Fix UMR cleanup on error flow of driver init [2]  [  347.567063] infiniband mlx5_0: Couldn&amp;#39;t register device with driver model  [  347.591382] BUG: kernel NULL pointer dereference, address: 0000000000000020  [  347.593438] #PF: supervisor read access in kernel mode  [  347.595176] #PF: error_code(0x0000) - not-present page  [  347.596962] PGD 0 P4D 0  [  347.601361] RIP: 0010:ib_dealloc_pd_user+0x12/0xc0 [ib_core]  [  347.604171] RSP: 0018:ffff888106293b10 EFLAGS: 00010282  [  347.604834] RAX: 0000000000000000 RBX: 000000000000000e RCX: 0000000000000000  [  347.605672] RDX: ffff888106293ad0 RSI: 0000000000000000 RDI: 0000000000000000  [  347.606529] RBP: 0000000000000000 R08: ffff888106293ae0 R09: ffff888106293ae0  [  347.607379] R10: 0000000000000a06 R11: 0000000000000000 R12: 0000000000000000  [  347.608224] R13: ffffffffa0704dc0 R14: 0000000000000001 R15: 0000000000000001  [  347.609067] FS:  00007fdc720cd9c0(0000) GS:ffff88852c880000(0000) knlGS:0000000000000000  [  347.610094] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  [  347.610727] CR2: 0000000000000020 CR3: 000000010301200…&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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix UMR pd cleanup on error flow of driver init The cited commit moves the pd allocation from function mlx5r_umr_resource_cleanup() to a new function mlx5r_umr_cleanup(). So the fix in commit [1] is broken. In error flow, will hit panic [2]. Fix it by checking pd pointer to avoid panic if it is NULL; [1] RDMA/mlx5: Fix UMR cleanup on error flow of driver init [2]  [  347.567063] infiniband mlx5_0: Couldn&amp;#39;t register device with driver model  [  347.591382] BUG: kernel NULL pointer dereference, address: 0000000000000020  [  347.593438] #PF: supervisor read access in kernel mode  [  347.595176] #PF: error_code(0x0000) - not-present page  [  347.596962] PGD 0 P4D 0  [  347.601361] RIP: 0010:ib_dealloc_pd_user+0x12/0xc0 [ib_core]  [  347.604171] RSP: 0018:ffff888106293b10 EFLAGS: 00010282  [  347.604834] RAX: 0000000000000000 RBX: 000000000000000e RCX: 0000000000000000  [  347.605672] RDX: ffff888106293ad0 RSI: 0000000000000000 RDI: 0000000000000000  [  347.606529] RBP: 0000000000000000 R08: ffff888106293ae0 R09: ffff888106293ae0  [  347.607379] R10: 0000000000000a06 R11: 0000000000000000 R12: 0000000000000000  [  347.608224] R13: ffffffffa0704dc0 R14: 0000000000000001 R15: 0000000000000001  [  347.609067] FS:  00007fdc720cd9c0(0000) GS:ffff88852c880000(0000) knlGS:0000000000000000  [  347.610094] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  [  347.610727] CR2: 0000000000000020 CR3: 000000010301200…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-47694</guid>
    </item>
  </channel>
</rss>
