<?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 14:33:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74717</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74717</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-2026-74717</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — 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-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74717</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74717</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fw_tracer, return NULL on create error Tracer creation can fail by returning either NULL or ERR_PTR. The return value is stored without a check on the device, and users treat ERR_PTR and NULL the same way. This also causes a crash in the core dump logic, which is missing the ERR_PTR check and ends up dereferencing it, as shown in the trace below. Switch tracer creation to return NULL on failure only, so callers only need a single NULL check.   Internal error: Oops: 0000000096000006 [#1]  SMP   Modules linked in: mlx5_ib ib_uverbs ib_core ipv6 mlx5_core   CPU: 1 UID: 0 PID: 12 Comm: kworker/u16:0 Not tainted 6.19.7 #1 PREEMPT(none)   Workqueue: mlx5_health0001:01:00.0 mlx5_fw_reporter_err_work [mlx5_core]   pstate: a3400009 (NzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)   pc : mlx5_fw_tracer_trigger_core_dump_general+0x58/0xe0 [mlx5_core]   lr : mlx5_fw_tracer_trigger_core_dump_general+0x40/0xe0 [mlx5_core]   sp : ffff800081cf3c40   x29: ffff800081cf3c90 x28: 0000000000000000 x27: 0000000000000000   x26: ffff000080018828 x25: 0000000000000000 x24: ffff000080304a05   x23: ffff800081cf3d80 x22: ffff0000847e01a0 x21: 0000000000000000   x20: ffff0000847e01a0 x19: ffffffffffffffa1 x18: ffff80008310bbf0   x17: ffff800080119650 x16: ffff80008010df54 x15: ffff80008010d4ac   x14: ffff800079c202e4 x13: ffff80008002fe60 x12: ffff800080119650   x11: ffff80008010df54 x10: ffff80008010d4ac x9 : ffff800079c203d8…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fw_tracer, return NULL on create error Tracer creation can fail by returning either NULL or ERR_PTR. The return value is stored without a check on the device, and users treat ERR_PTR and NULL the same way. This also causes a crash in the core dump logic, which is missing the ERR_PTR check and ends up dereferencing it, as shown in the trace below. Switch tracer creation to return NULL on failure only, so callers only need a single NULL check.   Internal error: Oops: 0000000096000006 [#1]  SMP   Modules linked in: mlx5_ib ib_uverbs ib_core ipv6 mlx5_core   CPU: 1 UID: 0 PID: 12 Comm: kworker/u16:0 Not tainted 6.19.7 #1 PREEMPT(none)   Workqueue: mlx5_health0001:01:00.0 mlx5_fw_reporter_err_work [mlx5_core]   pstate: a3400009 (NzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)   pc : mlx5_fw_tracer_trigger_core_dump_general+0x58/0xe0 [mlx5_core]   lr : mlx5_fw_tracer_trigger_core_dump_general+0x40/0xe0 [mlx5_core]   sp : ffff800081cf3c40   x29: ffff800081cf3c90 x28: 0000000000000000 x27: 0000000000000000   x26: ffff000080018828 x25: 0000000000000000 x24: ffff000080304a05   x23: ffff800081cf3d80 x22: ffff0000847e01a0 x21: 0000000000000000   x20: ffff0000847e01a0 x19: ffffffffffffffa1 x18: ffff80008310bbf0   x17: ffff800080119650 x16: ffff80008010df54 x15: ffff80008010d4ac   x14: ffff800079c202e4 x13: ffff80008002fe60 x12: ffff800080119650   x11: ffff80008010df54 x10: ffff80008010d4ac x9 : ffff800079c203d8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74717</guid>
    </item>
  </channel>
</rss>
