<?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 03:17:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-39480</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-39480</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-39480</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — 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-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2024-1860 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1860</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;
RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests&#13;
&#13;
The FSM can run in a circle allowing rdma_resolve_ip() to be called twice
on the same id_priv. While this cannot happen without going through the
work, it violates the invariant that the same address resolution
background request cannot be active twice.&#13;
&#13;
       CPU 1                                  CPU 2&#13;
&#13;
rdma_resolve_addr():
  RDMA_CM_IDLE -&amp;amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)  #1&#13;
&#13;
			 process_one_req(): for #1
                          addr_handler():
                            RDMA_CM_ADDR_QUERY -&amp;amp;gt; RDMA_CM_ADDR_BOUND
                            mutex_unlock(&amp;amp;amp;id_priv-&amp;amp;gt;handler_mutex);
                            [.. handler still running ..]&#13;
&#13;
rdma_resolve_addr():
  RDMA_CM_ADDR_BOUND -&amp;amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)
    !! two requests are now on the req_list&#13;
&#13;
rdma_destroy_id():
 destroy_id_handler_unlock():
  _destroy_id():
   cma_cancel_operation():
    rdma_addr_cancel()&#13;
&#13;
                          // process_one_req() self removes it
		          spin_lock_bh(&amp;amp;amp;lock);
                           cancel_delayed_work(&amp;amp;amp;req-&amp;amp;gt;work);
	                   if (!list_empty(&amp;amp;amp;req-&amp;amp;gt;list)) == true&#13;
&#13;
      ! rdma_addr_cancel() returns after process_on_req #1 is done&#13;
&#13;
   kfree(id_priv…&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;
RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests&#13;
&#13;
The FSM can run in a circle allowing rdma_resolve_ip() to be called twice
on the same id_priv. While this cannot happen without going through the
work, it violates the invariant that the same address resolution
background request cannot be active twice.&#13;
&#13;
       CPU 1                                  CPU 2&#13;
&#13;
rdma_resolve_addr():
  RDMA_CM_IDLE -&amp;amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)  #1&#13;
&#13;
			 process_one_req(): for #1
                          addr_handler():
                            RDMA_CM_ADDR_QUERY -&amp;amp;gt; RDMA_CM_ADDR_BOUND
                            mutex_unlock(&amp;amp;amp;id_priv-&amp;amp;gt;handler_mutex);
                            [.. handler still running ..]&#13;
&#13;
rdma_resolve_addr():
  RDMA_CM_ADDR_BOUND -&amp;amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)
    !! two requests are now on the req_list&#13;
&#13;
rdma_destroy_id():
 destroy_id_handler_unlock():
  _destroy_id():
   cma_cancel_operation():
    rdma_addr_cancel()&#13;
&#13;
                          // process_one_req() self removes it
		          spin_lock_bh(&amp;amp;amp;lock);
                           cancel_delayed_work(&amp;amp;amp;req-&amp;amp;gt;work);
	                   if (!list_empty(&amp;amp;amp;req-&amp;amp;gt;list)) == true&#13;
&#13;
      ! rdma_addr_cancel() returns after process_on_req #1 is done&#13;
&#13;
   kfree(id_priv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1860</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-39480</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39480</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kdb: Fix buffer overflow during tab-complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kdb: Fix buffer overflow during tab-complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39480</guid>
    </item>
  </channel>
</rss>
