<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T19:45:09.568108+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0496</id>
    <title>certfr-2024-avi-0496 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-19T19:45:09.576501+00:00</updated>
    <content>certfr-2024-avi-0496</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0496"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-1860</id>
    <title>OESA-2024-1860 — kernel security update</title>
    <updated>2026-11-19T19:45:09.576572+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP1: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests

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.

       CPU 1                                  CPU 2

rdma_resolve_addr():
  RDMA_CM_IDLE -&amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)  #1

			 process_one_req(): for #1
                          addr_handler():
                            RDMA_CM_ADDR_QUERY -&amp;gt; RDMA_CM_ADDR_BOUND
                            mutex_unlock(&amp;amp;id_priv-&amp;gt;handler_mutex);
                            [.. handler still running ..]

rdma_resolve_addr():
  RDMA_CM_ADDR_BOUND -&amp;gt; RDMA_CM_ADDR_QUERY
  rdma_resolve_ip(addr_handler)
    !! two requests are now on the req_list

rdma_destroy_id():
 destroy_id_handler_unlock():
  _destroy_id():
   cma_cancel_operation():
    rdma_addr_cancel()

                          // process_one_req() self removes it
		          spin_lock_bh(&amp;amp;lock);
                           cancel_delayed_work(&amp;amp;req-&amp;gt;work);
	                   if (!list_empty(&amp;amp;req-&amp;gt;list)) == true

      ! rdma_addr_cancel() returns after process_on_req #1 is done

   kfree(id_priv…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-1860"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2021-47391</id>
    <title>UBUNTU-CVE-2021-47391</title>
    <updated>2026-11-19T19:45:09.576800+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 112 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests 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.        CPU 1                                  CPU 2 rdma_resolve_addr():   RDMA_CM_IDLE -&gt; RDMA_CM_ADDR_QUERY   rdma_resolve_ip(addr_handler)  #1 			 process_one_req(): for #1                           addr_handler():                             RDMA_CM_ADDR_QUERY -&gt; RDMA_CM_ADDR_BOUND                             mutex_unlock(&amp;id_priv-&gt;handler_mutex);                             [.. handler still running ..] rdma_resolve_addr():   RDMA_CM_ADDR_BOUND -&gt; RDMA_CM_ADDR_QUERY   rdma_resolve_ip(addr_handler)     !! two requests are now on the req_list rdma_destroy_id():  destroy_id_handler_unlock():   _destroy_id():    cma_cancel_operation():     rdma_addr_cancel()                           // process_one_req() self removes it 		          spin_lock_bh(&amp;lock);                            cancel_delayed_work(&amp;req-&gt;work); 	                   if (!list_empty(&amp;req-&gt;list)) == true       ! rdma_addr_cancel() returns after process_on_req #1 is done    kfree(id_priv) 			 process_one_req(): for #2                           addr_handler(): 	                    mutex_lock(&amp;id_priv-&gt;handler_mutex);…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2021-47391"/>
  </entry>
</feed>
