<?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 00:47:00 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-36478</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36478</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-36478</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</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-36478</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36478</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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: null_blk: fix null-ptr-dereference while configuring &amp;#39;power&amp;#39; and &amp;#39;submit_queues&amp;#39; Writing &amp;#39;power&amp;#39; and &amp;#39;submit_queues&amp;#39; concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 &amp;gt; submit_queues; echo 4 &amp;gt; submit_queues; done &amp;amp; while true; do echo 1 &amp;gt; power; echo 0 &amp;gt; power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace:  &amp;lt;TASK&amp;gt;  lock_acquire+0x121/0x450  down_write+0x5f/0x1d0  simple_recursive_removal+0x12f/0x5c0  blk_mq_debugfs_unregister_hctxs+0x7c/0x100  blk_mq_update_nr_hw_queues+0x4a3/0x720  nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]  nullb_device_submit_queues_store+0x79/0xf0 [null_blk]  configfs_write_iter+0x119/0x1e0  vfs_write+0x326/0x730  ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store	nullb_apply_submit_queues  null_del_dev  del_gendisk 				 nullb_update_nr_hw_queues 				  if (!dev-&amp;gt;nullb) 				  // still set while gendisk is deleted 				   return 0 				  blk_mq_update_nr_hw_queues  dev-&amp;gt;nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.&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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: null_blk: fix null-ptr-dereference while configuring &amp;#39;power&amp;#39; and &amp;#39;submit_queues&amp;#39; Writing &amp;#39;power&amp;#39; and &amp;#39;submit_queues&amp;#39; concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 &amp;gt; submit_queues; echo 4 &amp;gt; submit_queues; done &amp;amp; while true; do echo 1 &amp;gt; power; echo 0 &amp;gt; power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace:  &amp;lt;TASK&amp;gt;  lock_acquire+0x121/0x450  down_write+0x5f/0x1d0  simple_recursive_removal+0x12f/0x5c0  blk_mq_debugfs_unregister_hctxs+0x7c/0x100  blk_mq_update_nr_hw_queues+0x4a3/0x720  nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]  nullb_device_submit_queues_store+0x79/0xf0 [null_blk]  configfs_write_iter+0x119/0x1e0  vfs_write+0x326/0x730  ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store	nullb_apply_submit_queues  null_del_dev  del_gendisk 				 nullb_update_nr_hw_queues 				  if (!dev-&amp;gt;nullb) 				  // still set while gendisk is deleted 				   return 0 				  blk_mq_update_nr_hw_queues  dev-&amp;gt;nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36478</guid>
    </item>
  </channel>
</rss>
