<?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>Fri, 20 Nov 2026 22:27:43 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38440</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38440</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-38440</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38440</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38440</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 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix race between DIM disable and net_dim() There&amp;#39;s a race between disabling DIM and NAPI callbacks using the dim pointer on the RQ or SQ. If NAPI checks the DIM state bit and sees it still set, it assumes `rq-&amp;gt;dim` or `sq-&amp;gt;dim` is valid. But if DIM gets disabled right after that check, the pointer might already be set to NULL, leading to a NULL pointer dereference in net_dim(). Fix this by calling `synchronize_net()` before freeing the DIM context. This ensures all in-progress NAPI callbacks are finished before the pointer is cleared. Kernel log: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... RIP: 0010:net_dim+0x23/0x190 ... Call Trace:  &amp;lt;TASK&amp;gt;  ? __die+0x20/0x60  ? page_fault_oops+0x150/0x3e0  ? common_interrupt+0xf/0xa0  ? sysvec_call_function_single+0xb/0x90  ? exc_page_fault+0x74/0x130  ? asm_exc_page_fault+0x22/0x30  ? net_dim+0x23/0x190  ? mlx5e_poll_ico_cq+0x41/0x6f0 [mlx5_core]  ? sysvec_apic_timer_interrupt+0xb/0x90  mlx5e_handle_rx_dim+0x92/0xd0 [mlx5_core]  mlx5e_napi_poll+0x2cd/0xac0 [mlx5_core]  ? mlx5e_poll_ico_cq+0xe5/0x6f0 [mlx5_core]  busy_poll_stop+0xa2/0x200  ? mlx5e_napi_poll+0x1d9/0xac0 [mlx5_core]  ? mlx5e_trigger_irq+0x130/0x130 [mlx5_core]  __napi_busy_loop+0x345/0x3b0  ? sysvec_call_function_single+0xb/0x90  ? asm_sysvec_call_function_single+0x16/0x20  ? sysvec_apic_timer_interrupt+0xb/0x90  ? pcpu_free_area+0x1e4/0x2e0  napi_busy_loop+0x11/0x20  xsk_r…&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 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix race between DIM disable and net_dim() There&amp;#39;s a race between disabling DIM and NAPI callbacks using the dim pointer on the RQ or SQ. If NAPI checks the DIM state bit and sees it still set, it assumes `rq-&amp;gt;dim` or `sq-&amp;gt;dim` is valid. But if DIM gets disabled right after that check, the pointer might already be set to NULL, leading to a NULL pointer dereference in net_dim(). Fix this by calling `synchronize_net()` before freeing the DIM context. This ensures all in-progress NAPI callbacks are finished before the pointer is cleared. Kernel log: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... RIP: 0010:net_dim+0x23/0x190 ... Call Trace:  &amp;lt;TASK&amp;gt;  ? __die+0x20/0x60  ? page_fault_oops+0x150/0x3e0  ? common_interrupt+0xf/0xa0  ? sysvec_call_function_single+0xb/0x90  ? exc_page_fault+0x74/0x130  ? asm_exc_page_fault+0x22/0x30  ? net_dim+0x23/0x190  ? mlx5e_poll_ico_cq+0x41/0x6f0 [mlx5_core]  ? sysvec_apic_timer_interrupt+0xb/0x90  mlx5e_handle_rx_dim+0x92/0xd0 [mlx5_core]  mlx5e_napi_poll+0x2cd/0xac0 [mlx5_core]  ? mlx5e_poll_ico_cq+0xe5/0x6f0 [mlx5_core]  busy_poll_stop+0xa2/0x200  ? mlx5e_napi_poll+0x1d9/0xac0 [mlx5_core]  ? mlx5e_trigger_irq+0x130/0x130 [mlx5_core]  __napi_busy_loop+0x345/0x3b0  ? sysvec_call_function_single+0xb/0x90  ? asm_sysvec_call_function_single+0x16/0x20  ? sysvec_apic_timer_interrupt+0xb/0x90  ? pcpu_free_area+0x1e4/0x2e0  napi_busy_loop+0x11/0x20  xsk_r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38440</guid>
    </item>
  </channel>
</rss>
