<?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 21:01:11 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-38634</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-38634</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-38634</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0527 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</link>
      <description>certfr-2024-avi-0527</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</guid>
    </item>
    <item>
      <title>OESA-2024-1768 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1768</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ASoC: SOF: Fix DSP oops stack dump output contents&#13;
&#13;
Fix @buf arg given to hex_dump_to_buffer() and stack address used
in dump error output.(CVE-2021-47381)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: iscsi: Fix iscsi_task use after free&#13;
&#13;
Commit d39df158518c (&amp;amp;quot;scsi: iscsi: Have abort handler get ref to conn&amp;amp;quot;)
added iscsi_get_conn()/iscsi_put_conn() calls during abort handling but
then also changed the handling of the case where we detect an already
completed task where we now end up doing a goto to the common put/cleanup
code. This results in a iscsi_task use after free, because the common
cleanup code will do a put on the iscsi_task.&#13;
&#13;
This reverts the goto and moves the iscsi_get_conn() to after we&amp;amp;apos;ve checked
if the iscsi_task is valid.(CVE-2021-47427)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ASoC: SOF: Fix DSP oops stack dump output contents&#13;
&#13;
Fix @buf arg given to hex_dump_to_buffer() and stack address used
in dump error output.(CVE-2021-47381)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: iscsi: Fix iscsi_task use after free&#13;
&#13;
Commit d39df158518c (&amp;amp;quot;scsi: iscsi: Have abort handler get ref to conn&amp;amp;quot;)
added iscsi_get_conn()/iscsi_put_conn() calls during abort handling but
then also changed the handling of the case where we detect an already
completed task where we now end up doing a goto to the common put/cleanup
code. This results in a iscsi_task use after free, because the common
cleanup code will do a put on the iscsi_task.&#13;
&#13;
This reverts the goto and moves the iscsi_get_conn() to after we&amp;amp;apos;ve checked
if the iscsi_task is valid.(CVE-2021-47427)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1768</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-38634</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38634</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port-&amp;gt;lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it&amp;#39;s taken by explicitly doing that. Without it we got a splat:   WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0   ...   Workqueue: max3100-0 max3100_work [max3100]   RIP: 0010:uart_handle_cts_change+0xa6/0xb0   ...    max3100_handlerx+0xc5/0x110 [max3100]    max3100_work+0x12a/0x340 [max3100]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port-&amp;gt;lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it&amp;#39;s taken by explicitly doing that. Without it we got a splat:   WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0   ...   Workqueue: max3100-0 max3100_work [max3100]   RIP: 0010:uart_handle_cts_change+0xa6/0xb0   ...    max3100_handlerx+0xc5/0x110 [max3100]    max3100_work+0x12a/0x340 [max3100]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38634</guid>
    </item>
  </channel>
</rss>
