<?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 16:50:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-53344</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-53344</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2023-53344</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</guid>
    </item>
    <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-2023-53344</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53344</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write Syzkaller reported the following issue: ===================================================== BUG: KMSAN: uninit-value in aio_rw_done fs/aio.c:1520 [inline] BUG: KMSAN: uninit-value in aio_write+0x899/0x950 fs/aio.c:1600  aio_rw_done fs/aio.c:1520 [inline]  aio_write+0x899/0x950 fs/aio.c:1600  io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019  __do_sys_io_submit fs/aio.c:2078 [inline]  __se_sys_io_submit+0x293/0x770 fs/aio.c:2048  __x64_sys_io_submit+0x92/0xd0 fs/aio.c:2048  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd Uninit was created at:  slab_post_alloc_hook mm/slab.h:766 [inline]  slab_alloc_node mm/slub.c:3452 [inline]  __kmem_cache_alloc_node+0x71f/0xce0 mm/slub.c:3491  __do_kmalloc_node mm/slab_common.c:967 [inline]  __kmalloc+0x11d/0x3b0 mm/slab_common.c:981  kmalloc_array include/linux/slab.h:636 [inline]  bcm_tx_setup+0x80e/0x29d0 net/can/bcm.c:930  bcm_sendmsg+0x3a2/0xce0 net/can/bcm.c:1351  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendmsg net/socket.c:734 [inline]  sock_write_iter+0x495/0x5e0 net/socket.c:1108  call_write_iter include/linux/fs.h:2189 [inline]  aio_write+0x63a/0x950 fs/aio.c:1600  io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019  __do_sys_io_submit fs/aio.c:2078 [inline]  __se_sys_io_submit+0x293/0x770 fs/aio.c:2048  __x64_s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write Syzkaller reported the following issue: ===================================================== BUG: KMSAN: uninit-value in aio_rw_done fs/aio.c:1520 [inline] BUG: KMSAN: uninit-value in aio_write+0x899/0x950 fs/aio.c:1600  aio_rw_done fs/aio.c:1520 [inline]  aio_write+0x899/0x950 fs/aio.c:1600  io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019  __do_sys_io_submit fs/aio.c:2078 [inline]  __se_sys_io_submit+0x293/0x770 fs/aio.c:2048  __x64_sys_io_submit+0x92/0xd0 fs/aio.c:2048  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd Uninit was created at:  slab_post_alloc_hook mm/slab.h:766 [inline]  slab_alloc_node mm/slub.c:3452 [inline]  __kmem_cache_alloc_node+0x71f/0xce0 mm/slub.c:3491  __do_kmalloc_node mm/slab_common.c:967 [inline]  __kmalloc+0x11d/0x3b0 mm/slab_common.c:981  kmalloc_array include/linux/slab.h:636 [inline]  bcm_tx_setup+0x80e/0x29d0 net/can/bcm.c:930  bcm_sendmsg+0x3a2/0xce0 net/can/bcm.c:1351  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendmsg net/socket.c:734 [inline]  sock_write_iter+0x495/0x5e0 net/socket.c:1108  call_write_iter include/linux/fs.h:2189 [inline]  aio_write+0x63a/0x950 fs/aio.c:1600  io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019  __do_sys_io_submit fs/aio.c:2078 [inline]  __se_sys_io_submit+0x293/0x770 fs/aio.c:2048  __x64_s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53344</guid>
    </item>
  </channel>
</rss>
