<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 15:43:14 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10378</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-10378</link>
      <description>bdu:2026-10378</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-10378</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50639</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50639</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2022-50639</guid>
    </item>
    <item>
      <title>GHSA-556c-4mvg-6pqr</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-556c-4mvg-6pqr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-556c-4mvg-6pqr</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50639</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50639</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 102 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array. This was spotted when fuzzing v6.1-rc1 with Syzkaller: BUG: memory leak unreferenced object 0xffff8880093d5000 (size 1024):   comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720     [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130     [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0     [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d     [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba     [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce     [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80     [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90     [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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 102 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array. This was spotted when fuzzing v6.1-rc1 with Syzkaller: BUG: memory leak unreferenced object 0xffff8880093d5000 (size 1024):   comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720     [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130     [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0     [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d     [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba     [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce     [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80     [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90     [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50639</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765</guid>
    </item>
  </channel>
</rss>
