<?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:11:27 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:4583 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:4583</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
  * kernel: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() (CVE-2021-47548)
  * kernel: net: hns3: fix use-after-free bug in hclgevf_send_mbx_msg (CVE-2021-47596)
  * kernel: vt: fix memory overlapping when deleting chars in the buffer (CVE-2022-48627)
  * kernel: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock (CVE-2023-52638)
  * kernel: mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index (CVE-2024-26783)
  * kernel: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map (CVE-2024-26858)
  * kernel: netfilter: nf_tables: use timestamp to check for set element timeout (CVE-2024-27397)
  * kernel: nvme: fix reconnection fail due to reserved tag allocation (CVE-2024-27435)
  * kernel: net: ena: Fix incorrect descriptor free behavior (CVE-2024-35958)
  * kernel: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). (CVE-2024-36904)
  * kernel: lib/test_hmm.c: handle src_pfns and dst_pfns allocation failure (CVE-2024-38543)
  * kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
  * kernel: net: micrel: Fix receiving the timestamp in the frame for lan8841 (CVE-2024-38593)
  *…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
  * kernel: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() (CVE-2021-47548)
  * kernel: net: hns3: fix use-after-free bug in hclgevf_send_mbx_msg (CVE-2021-47596)
  * kernel: vt: fix memory overlapping when deleting chars in the buffer (CVE-2022-48627)
  * kernel: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock (CVE-2023-52638)
  * kernel: mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index (CVE-2024-26783)
  * kernel: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map (CVE-2024-26858)
  * kernel: netfilter: nf_tables: use timestamp to check for set element timeout (CVE-2024-27397)
  * kernel: nvme: fix reconnection fail due to reserved tag allocation (CVE-2024-27435)
  * kernel: net: ena: Fix incorrect descriptor free behavior (CVE-2024-35958)
  * kernel: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). (CVE-2024-36904)
  * kernel: lib/test_hmm.c: handle src_pfns and dst_pfns allocation failure (CVE-2024-38543)
  * kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
  * kernel: net: micrel: Fix receiving the timestamp in the frame for lan8841 (CVE-2024-38593)
  *…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:4583</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-38586</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-38586</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-38586</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0612 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0612</link>
      <description>certfr-2024-avi-0612</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0612</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-38586</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38586</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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: r8169: Fix possible ring buffer corruption on fragmented Tx packets. An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address. This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2(). To fix this, postpone inspecting nr_frags until after any padding has been applied.&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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: r8169: Fix possible ring buffer corruption on fragmented Tx packets. An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address. This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2(). To fix this, postpone inspecting nr_frags until after any padding has been applied.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38586</guid>
    </item>
  </channel>
</rss>
