<?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 06:04:51 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-36930</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36930</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-36930</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36930</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36930</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spi: fix null pointer dereference within spi_sync If spi_sync() is called with the non-empty queue and the same spi_message is then reused, the complete callback for the message remains set while the context is cleared, leading to a null pointer dereference when the callback is invoked from spi_finalize_current_message(). With function inlining disabled, the call stack might look like this:   _raw_spin_lock_irqsave from complete_with_flags+0x18/0x58   complete_with_flags from spi_complete+0x8/0xc   spi_complete from spi_finalize_current_message+0xec/0x184   spi_finalize_current_message from spi_transfer_one_message+0x2a8/0x474   spi_transfer_one_message from __spi_pump_transfer_message+0x104/0x230   __spi_pump_transfer_message from __spi_transfer_message_noqueue+0x30/0xc4   __spi_transfer_message_noqueue from __spi_sync+0x204/0x248   __spi_sync from spi_sync+0x24/0x3c   spi_sync from mcp251xfd_regmap_crc_read+0x124/0x28c [mcp251xfd]   mcp251xfd_regmap_crc_read [mcp251xfd] from _regmap_raw_read+0xf8/0x154   _regmap_raw_read from _regmap_bus_read+0x44/0x70   _regmap_bus_read from _regmap_read+0x60/0xd8   _regmap_read from regmap_read+0x3c/0x5c   regmap_read from mcp251xfd_alloc_can_err_skb+0x1c/0x54 [mcp251xfd]   mcp251xfd_alloc_can_err_skb [mcp251xfd] from mcp251xfd_irq+0x194/0xe70 [mcp251xfd]   mcp251xfd_irq [mcp251xfd] from irq_thread_fn+0x1c/0x78   irq_thread_fn from irq_thread+0x118/0x1f4   irq_thread fro…&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spi: fix null pointer dereference within spi_sync If spi_sync() is called with the non-empty queue and the same spi_message is then reused, the complete callback for the message remains set while the context is cleared, leading to a null pointer dereference when the callback is invoked from spi_finalize_current_message(). With function inlining disabled, the call stack might look like this:   _raw_spin_lock_irqsave from complete_with_flags+0x18/0x58   complete_with_flags from spi_complete+0x8/0xc   spi_complete from spi_finalize_current_message+0xec/0x184   spi_finalize_current_message from spi_transfer_one_message+0x2a8/0x474   spi_transfer_one_message from __spi_pump_transfer_message+0x104/0x230   __spi_pump_transfer_message from __spi_transfer_message_noqueue+0x30/0xc4   __spi_transfer_message_noqueue from __spi_sync+0x204/0x248   __spi_sync from spi_sync+0x24/0x3c   spi_sync from mcp251xfd_regmap_crc_read+0x124/0x28c [mcp251xfd]   mcp251xfd_regmap_crc_read [mcp251xfd] from _regmap_raw_read+0xf8/0x154   _regmap_raw_read from _regmap_bus_read+0x44/0x70   _regmap_bus_read from _regmap_read+0x60/0xd8   _regmap_read from regmap_read+0x3c/0x5c   regmap_read from mcp251xfd_alloc_can_err_skb+0x1c/0x54 [mcp251xfd]   mcp251xfd_alloc_can_err_skb [mcp251xfd] from mcp251xfd_irq+0x194/0xe70 [mcp251xfd]   mcp251xfd_irq [mcp251xfd] from irq_thread_fn+0x1c/0x78   irq_thread_fn from irq_thread+0x118/0x1f4   irq_thread fro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36930</guid>
    </item>
  </channel>
</rss>
