<?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 02:39:26 +0000</lastBuildDate>
    <item>
      <title>OESA-2025-2805 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2805</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: handle the error returned from sctp_auth_asoc_init_active_key&lt;/p&gt;
&lt;p&gt;When it returns an error from sctp_auth_asoc_init_active_key(), the
active_key is actually not updated. The old sh_key will be freeed
while it&amp;amp;apos;s still used as active key in asoc. Then an use-after-free
will be triggered when sending patckets, as found by syzbot:&lt;/p&gt;
&lt;p&gt;sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
  sctp_set_owner_w net/sctp/socket.c:132 [inline]
  sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863
  sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025
  inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819
  sock_sendmsg_nosec net/socket.c:714 [inline]
  sock_sendmsg+0xcf/0x120 net/socket.c:734&lt;/p&gt;
&lt;p&gt;This patch is to fix it by not replacing the sh_key when it returns
errors from sctp_auth_asoc_init_active_key() in sctp_auth_set_key().
For sctp_auth_set_active_key(), old active_key_id will be set back
to asoc-&amp;amp;gt;active_key_id when the same thing happens.(CVE-2022-50243)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Do not free q_vector unless new one was allocated&lt;/p&gt;
&lt;p&gt;Avoid potential use-after-free condition under memory pressure. If the
kzalloc() fails, q_vector will be freed but left in the original
adapter-&amp;amp;gt;q_vector[v_idx] array position.(CVE-2022-50252)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: handle the error returned from sctp_auth_asoc_init_active_key&lt;/p&gt;
&lt;p&gt;When it returns an error from sctp_auth_asoc_init_active_key(), the
active_key is actually not updated. The old sh_key will be freeed
while it&amp;amp;apos;s still used as active key in asoc. Then an use-after-free
will be triggered when sending patckets, as found by syzbot:&lt;/p&gt;
&lt;p&gt;sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
  sctp_set_owner_w net/sctp/socket.c:132 [inline]
  sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863
  sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025
  inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819
  sock_sendmsg_nosec net/socket.c:714 [inline]
  sock_sendmsg+0xcf/0x120 net/socket.c:734&lt;/p&gt;
&lt;p&gt;This patch is to fix it by not replacing the sh_key when it returns
errors from sctp_auth_asoc_init_active_key() in sctp_auth_set_key().
For sctp_auth_set_active_key(), old active_key_id will be set back
to asoc-&amp;amp;gt;active_key_id when the same thing happens.(CVE-2022-50243)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igb: Do not free q_vector unless new one was allocated&lt;/p&gt;
&lt;p&gt;Avoid potential use-after-free condition under memory pressure. If the
kzalloc() fails, q_vector will be freed but left in the original
adapter-&amp;amp;gt;q_vector[v_idx] array position.(CVE-2022-50252)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2805</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50555</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50555</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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: fix a null-ptr-deref in tipc_topsrv_accept syzbot found a crash in tipc_topsrv_accept:   KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]   Workqueue: tipc_rcv tipc_topsrv_accept   RIP: 0010:kernel_accept+0x22d/0x350 net/socket.c:3487   Call Trace:    &amp;lt;TASK&amp;gt;    tipc_topsrv_accept+0x197/0x280 net/tipc/topsrv.c:460    process_one_work+0x991/0x1610 kernel/workqueue.c:2289    worker_thread+0x665/0x1080 kernel/workqueue.c:2436    kthread+0x2e4/0x3a0 kernel/kthread.c:376    ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 It was caused by srv-&amp;gt;listener that might be set to null by tipc_topsrv_stop() in net .exit whereas it&amp;#39;s still used in tipc_topsrv_accept() worker. srv-&amp;gt;listener is protected by srv-&amp;gt;idr_lock in tipc_topsrv_stop(), so add a check for srv-&amp;gt;listener under srv-&amp;gt;idr_lock in tipc_topsrv_accept() to avoid the null-ptr-deref. To ensure the lsock is not released during the tipc_topsrv_accept(), move sock_release() after tipc_topsrv_work_stop() where it&amp;#39;s waiting until the tipc_topsrv_accept worker to be done. Note that sk_callback_lock is used to protect sk-&amp;gt;sk_user_data instead of srv-&amp;gt;listener, and it should check srv in tipc_topsrv_listener_data_ready() instead. This also ensures that no more tipc_topsrv_accept worker will be started after tipc_conn_close() is called in tipc_topsrv_stop() where it sets sk-&amp;gt;sk_user_data to null.&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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: fix a null-ptr-deref in tipc_topsrv_accept syzbot found a crash in tipc_topsrv_accept:   KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]   Workqueue: tipc_rcv tipc_topsrv_accept   RIP: 0010:kernel_accept+0x22d/0x350 net/socket.c:3487   Call Trace:    &amp;lt;TASK&amp;gt;    tipc_topsrv_accept+0x197/0x280 net/tipc/topsrv.c:460    process_one_work+0x991/0x1610 kernel/workqueue.c:2289    worker_thread+0x665/0x1080 kernel/workqueue.c:2436    kthread+0x2e4/0x3a0 kernel/kthread.c:376    ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 It was caused by srv-&amp;gt;listener that might be set to null by tipc_topsrv_stop() in net .exit whereas it&amp;#39;s still used in tipc_topsrv_accept() worker. srv-&amp;gt;listener is protected by srv-&amp;gt;idr_lock in tipc_topsrv_stop(), so add a check for srv-&amp;gt;listener under srv-&amp;gt;idr_lock in tipc_topsrv_accept() to avoid the null-ptr-deref. To ensure the lsock is not released during the tipc_topsrv_accept(), move sock_release() after tipc_topsrv_work_stop() where it&amp;#39;s waiting until the tipc_topsrv_accept worker to be done. Note that sk_callback_lock is used to protect sk-&amp;gt;sk_user_data instead of srv-&amp;gt;listener, and it should check srv in tipc_topsrv_listener_data_ready() instead. This also ensures that no more tipc_topsrv_accept worker will be started after tipc_conn_close() is called in tipc_topsrv_stop() where it sets sk-&amp;gt;sk_user_data to null.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50555</guid>
    </item>
  </channel>
</rss>
