<?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://cve.radiocsirt.org</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 20:52:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05782</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05782</link>
      <description>bdu:2026-05782</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05782</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0529 — 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://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</link>
      <description>certfr-2025-avi-0529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</guid>
    </item>
    <item>
      <title>EUVD-2026-310894</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310894</link>
      <description>EUVD-2026-310894</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310894</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49901</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49901</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d
    [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392
    [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_realloc_hw_ctxs
      for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {
        old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);
        if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&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;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d
    [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392
    [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_realloc_hw_ctxs
      for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {
        old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);
        if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49901</guid>
    </item>
    <item>
      <title>GHSA-pmj7-4375-32j4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pmj7-4375-32j4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d
    [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392
    [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_realloc_hw_ctxs
      for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {
        old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);
        if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&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;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d
    [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392
    [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_realloc_hw_ctxs
      for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {
        old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);
        if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pmj7-4375-32j4</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-49901 — blk-mq: Fix kmemleak in blk_mq_init_allocated_queue</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-49901</link>
      <description>msrc_CVE-2022-49901</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-49901</guid>
    </item>
    <item>
      <title>OESA-2025-1514 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1514</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;amp;quot;modprobe&amp;amp;quot;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;amp;lt;000000004a10c249&amp;amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;amp;lt;00000000648f7950&amp;amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;amp;lt;00000000af06de0e&amp;amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;amp;lt;00000000e00c1872&amp;amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;amp;lt;00000000d16b4e68&amp;amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;amp;lt;00000000d10c98c3&amp;amp;gt;] 0xffffffffc450d69d
    [&amp;amp;lt;00000000b9299f48&amp;amp;gt;] 0xffffffffc4538392
    [&amp;amp;lt;0000000061c39ed6&amp;amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;amp;lt;00000000b389383b&amp;amp;gt;] do_init_module+0x1a4/0x680
    [&amp;amp;lt;0000000087cf3542&amp;amp;gt;] load_module+0x6249/0x7110
    [&amp;amp;lt;00000000beba61b8&amp;amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;amp;lt;00000000fdcfff51&amp;amp;gt;] do_syscall_64+0x35/0x80
    [&amp;amp;lt;000000003c0f1f71&amp;amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_reall…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;blk-mq: Fix kmemleak in blk_mq_init_allocated_queue&lt;/p&gt;
&lt;p&gt;There is a kmemleak caused by modprobe null_blk.ko&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881acb1f000 (size 1024):
  comm &amp;amp;quot;modprobe&amp;amp;quot;, pid 836, jiffies 4294971190 (age 27.068s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......
  backtrace:
    [&amp;amp;lt;000000004a10c249&amp;amp;gt;] kmalloc_node_trace+0x22/0x60
    [&amp;amp;lt;00000000648f7950&amp;amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350
    [&amp;amp;lt;00000000af06de0e&amp;amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
    [&amp;amp;lt;00000000e00c1872&amp;amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440
    [&amp;amp;lt;00000000d16b4e68&amp;amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0
    [&amp;amp;lt;00000000d10c98c3&amp;amp;gt;] 0xffffffffc450d69d
    [&amp;amp;lt;00000000b9299f48&amp;amp;gt;] 0xffffffffc4538392
    [&amp;amp;lt;0000000061c39ed6&amp;amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;amp;lt;00000000b389383b&amp;amp;gt;] do_init_module+0x1a4/0x680
    [&amp;amp;lt;0000000087cf3542&amp;amp;gt;] load_module+0x6249/0x7110
    [&amp;amp;lt;00000000beba61b8&amp;amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;amp;lt;00000000fdcfff51&amp;amp;gt;] do_syscall_64+0x35/0x80
    [&amp;amp;lt;000000003c0f1f71&amp;amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;That is because q-&amp;amp;gt;ma_ops is set to NULL before blk_release_queue is
called.&lt;/p&gt;
&lt;p&gt;blk_mq_init_queue_data
  blk_mq_init_allocated_queue
    blk_mq_reall…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1514</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01966-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01966-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01966-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49901</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49901</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 135 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: blk-mq: Fix kmemleak in blk_mq_init_allocated_queue There is a kmemleak caused by modprobe null_blk.ko unreferenced object 0xffff8881acb1f000 (size 1024):   comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)   hex dump (first 32 bytes):     00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........     ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......   backtrace:     [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60     [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350     [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0     [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440     [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0     [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d     [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392     [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0     [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680     [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110     [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200     [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is called. blk_mq_init_queue_data   blk_mq_init_allocated_queue     blk_mq_realloc_hw_ctxs       for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {         old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);         if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 135 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: blk-mq: Fix kmemleak in blk_mq_init_allocated_queue There is a kmemleak caused by modprobe null_blk.ko unreferenced object 0xffff8881acb1f000 (size 1024):   comm &amp;#34;modprobe&amp;#34;, pid 836, jiffies 4294971190 (age 27.068s)   hex dump (first 32 bytes):     00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........     ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff  .........S......   backtrace:     [&amp;lt;000000004a10c249&amp;gt;] kmalloc_node_trace+0x22/0x60     [&amp;lt;00000000648f7950&amp;gt;] blk_mq_alloc_and_init_hctx+0x289/0x350     [&amp;lt;00000000af06de0e&amp;gt;] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0     [&amp;lt;00000000e00c1872&amp;gt;] blk_mq_init_allocated_queue+0x48c/0x1440     [&amp;lt;00000000d16b4e68&amp;gt;] __blk_mq_alloc_disk+0xc8/0x1c0     [&amp;lt;00000000d10c98c3&amp;gt;] 0xffffffffc450d69d     [&amp;lt;00000000b9299f48&amp;gt;] 0xffffffffc4538392     [&amp;lt;0000000061c39ed6&amp;gt;] do_one_initcall+0xd0/0x4f0     [&amp;lt;00000000b389383b&amp;gt;] do_init_module+0x1a4/0x680     [&amp;lt;0000000087cf3542&amp;gt;] load_module+0x6249/0x7110     [&amp;lt;00000000beba61b8&amp;gt;] __do_sys_finit_module+0x140/0x200     [&amp;lt;00000000fdcfff51&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;000000003c0f1f71&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 That is because q-&amp;gt;ma_ops is set to NULL before blk_release_queue is called. blk_mq_init_queue_data   blk_mq_init_allocated_queue     blk_mq_realloc_hw_ctxs       for (i = 0; i &amp;lt; set-&amp;gt;nr_hw_queues; i++) {         old_hctx = xa_load(&amp;amp;q-&amp;gt;hctx_table, i);         if (!blk_mq_alloc_and_init_hctx(.., i, ..))		[1]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49901</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0922 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</guid>
    </item>
  </channel>
</rss>
