<?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 04:07:35 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26998</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26998</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-26998</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0611 — 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-2024-avi-0611</link>
      <description>certfr-2024-avi-0611</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0611</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26998</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26998</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 74 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: core: Clearing the circular buffer before NULLifying it The circular buffer is NULLified in uart_tty_port_shutdown() under the spin lock. However, the PM or other timer based callbacks may still trigger after this event without knowning that buffer pointer is not valid. Since the serial code is a bit inconsistent in checking the buffer state (some rely on the head-tail positions, some on the buffer pointer), it&amp;#39;s better to have both aligned, i.e. buffer pointer to be NULL and head-tail possitions to be the same, meaning it&amp;#39;s empty. This will prevent asynchronous calls to dereference NULL pointer as reported recently in 8250 case:   BUG: kernel NULL pointer dereference, address: 00000cf5   Workqueue: pm pm_runtime_work   EIP: serial8250_tx_chars (drivers/tty/serial/8250/8250_port.c:1809)   ...   ? serial8250_tx_chars (drivers/tty/serial/8250/8250_port.c:1809)   __start_tx (drivers/tty/serial/8250/8250_port.c:1551)   serial8250_start_tx (drivers/tty/serial/8250/8250_port.c:1654)   serial_port_runtime_suspend (include/linux/serial_core.h:667 drivers/tty/serial/serial_port.c:63)   __rpm_callback (drivers/base/power/runtime.c:393)   ? serial_port_remove (drivers/tty/serial/serial_port.c:50)   rpm_suspend (drivers/base/power/runtime.c:447) The proposed change will prevent -&amp;gt;start_tx() to be called during suspend on shut down port.&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 74 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: core: Clearing the circular buffer before NULLifying it The circular buffer is NULLified in uart_tty_port_shutdown() under the spin lock. However, the PM or other timer based callbacks may still trigger after this event without knowning that buffer pointer is not valid. Since the serial code is a bit inconsistent in checking the buffer state (some rely on the head-tail positions, some on the buffer pointer), it&amp;#39;s better to have both aligned, i.e. buffer pointer to be NULL and head-tail possitions to be the same, meaning it&amp;#39;s empty. This will prevent asynchronous calls to dereference NULL pointer as reported recently in 8250 case:   BUG: kernel NULL pointer dereference, address: 00000cf5   Workqueue: pm pm_runtime_work   EIP: serial8250_tx_chars (drivers/tty/serial/8250/8250_port.c:1809)   ...   ? serial8250_tx_chars (drivers/tty/serial/8250/8250_port.c:1809)   __start_tx (drivers/tty/serial/8250/8250_port.c:1551)   serial8250_start_tx (drivers/tty/serial/8250/8250_port.c:1654)   serial_port_runtime_suspend (include/linux/serial_core.h:667 drivers/tty/serial/serial_port.c:63)   __rpm_callback (drivers/base/power/runtime.c:393)   ? serial_port_remove (drivers/tty/serial/serial_port.c:50)   rpm_suspend (drivers/base/power/runtime.c:447) The proposed change will prevent -&amp;gt;start_tx() to be called during suspend on shut down port.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26998</guid>
    </item>
  </channel>
</rss>
