<?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>Thu, 19 Nov 2026 20:06:13 +0000</lastBuildDate>
    <item>
      <title>OESA-2025-2659 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2659</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;misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()&lt;/p&gt;
&lt;p&gt;If device_register() returns error in tifm_7xx1_switch_media(),
name of kobject which is allocated in dev_set_name() called in device_add()
is leaked.&lt;/p&gt;
&lt;p&gt;Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.(CVE-2022-50349)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;amp;quot;systemd-udevd&amp;amp;quot;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;amp;lt;0000000034783f26&amp;amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;amp;lt;00000000748188f2&amp;amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;amp;lt;00000000ab0743e8&amp;amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;amp;lt;000000006c0ffb13&amp;amp;gt;] kvasprintf+0x8c/0x118
    [&amp;amp;lt;00000000…&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;misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()&lt;/p&gt;
&lt;p&gt;If device_register() returns error in tifm_7xx1_switch_media(),
name of kobject which is allocated in dev_set_name() called in device_add()
is leaked.&lt;/p&gt;
&lt;p&gt;Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.(CVE-2022-50349)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;amp;quot;systemd-udevd&amp;amp;quot;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;amp;lt;0000000034783f26&amp;amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;amp;lt;00000000748188f2&amp;amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;amp;lt;00000000ab0743e8&amp;amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;amp;lt;000000006c0ffb13&amp;amp;gt;] kvasprintf+0x8c/0x118
    [&amp;amp;lt;00000000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2659</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50531</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50531</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 an information leak in tipc_topsrv_kern_subscr Use a 8-byte write to initialize sub.usr_handle in tipc_topsrv_kern_subscr(), otherwise four bytes remain uninitialized when issuing setsockopt(..., SOL_TIPC, ...). This resulted in an infoleak reported by KMSAN when the packet was received:   =====================================================   BUG: KMSAN: kernel-infoleak in copyout+0xbc/0x100 lib/iov_iter.c:169    instrument_copy_to_user ./include/linux/instrumented.h:121    copyout+0xbc/0x100 lib/iov_iter.c:169    _copy_to_iter+0x5c0/0x20a0 lib/iov_iter.c:527    copy_to_iter ./include/linux/uio.h:176    simple_copy_to_iter+0x64/0xa0 net/core/datagram.c:513    __skb_datagram_iter+0x123/0xdc0 net/core/datagram.c:419    skb_copy_datagram_iter+0x58/0x200 net/core/datagram.c:527    skb_copy_datagram_msg ./include/linux/skbuff.h:3903    packet_recvmsg+0x521/0x1e70 net/packet/af_packet.c:3469    ____sys_recvmsg+0x2c4/0x810 net/socket.c:?    ___sys_recvmsg+0x217/0x840 net/socket.c:2743    __sys_recvmsg net/socket.c:2773    __do_sys_recvmsg net/socket.c:2783    __se_sys_recvmsg net/socket.c:2780    __x64_sys_recvmsg+0x364/0x540 net/socket.c:2780    do_syscall_x64 arch/x86/entry/common.c:50    do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80    entry_SYSCALL_64_after_hwframe+0x63/0xcd arch/x86/entry/entry_64.S:120   ...   Uninit was stored to memory at:    tipc_sub_subscribe+0x42d/0xb50 net/tipc/subscr.c…&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 an information leak in tipc_topsrv_kern_subscr Use a 8-byte write to initialize sub.usr_handle in tipc_topsrv_kern_subscr(), otherwise four bytes remain uninitialized when issuing setsockopt(..., SOL_TIPC, ...). This resulted in an infoleak reported by KMSAN when the packet was received:   =====================================================   BUG: KMSAN: kernel-infoleak in copyout+0xbc/0x100 lib/iov_iter.c:169    instrument_copy_to_user ./include/linux/instrumented.h:121    copyout+0xbc/0x100 lib/iov_iter.c:169    _copy_to_iter+0x5c0/0x20a0 lib/iov_iter.c:527    copy_to_iter ./include/linux/uio.h:176    simple_copy_to_iter+0x64/0xa0 net/core/datagram.c:513    __skb_datagram_iter+0x123/0xdc0 net/core/datagram.c:419    skb_copy_datagram_iter+0x58/0x200 net/core/datagram.c:527    skb_copy_datagram_msg ./include/linux/skbuff.h:3903    packet_recvmsg+0x521/0x1e70 net/packet/af_packet.c:3469    ____sys_recvmsg+0x2c4/0x810 net/socket.c:?    ___sys_recvmsg+0x217/0x840 net/socket.c:2743    __sys_recvmsg net/socket.c:2773    __do_sys_recvmsg net/socket.c:2783    __se_sys_recvmsg net/socket.c:2780    __x64_sys_recvmsg+0x364/0x540 net/socket.c:2780    do_syscall_x64 arch/x86/entry/common.c:50    do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80    entry_SYSCALL_64_after_hwframe+0x63/0xcd arch/x86/entry/entry_64.S:120   ...   Uninit was stored to memory at:    tipc_sub_subscribe+0x42d/0xb50 net/tipc/subscr.c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50531</guid>
    </item>
  </channel>
</rss>
