<?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>Sat, 03 Oct 2026 03:04:19 +0000</lastBuildDate>
    <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-310895</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310895</link>
      <description>EUVD-2026-310895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310895</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49902</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49902</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: Fix possible memory leak for rq_wb on add_disk failure&lt;/p&gt;
&lt;p&gt;kmemleak reported memory leaks in device_add_disk():&lt;/p&gt;
&lt;p&gt;kmemleak: 3 new suspected memory leaks&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88800f420800 (size 512):
  comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)
  hex dump (first 32 bytes):
    04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................
    00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60
    [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0
    [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0
    [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420
    [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40
    [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]
    ...&lt;/p&gt;
&lt;p&gt;It is because the memory allocated in wbt_enable_default() is not
released in device_add_disk() error path.
Normally, these memory are freed in:&lt;/p&gt;
&lt;p&gt;del_gendisk()
  rq_qos_exit()
    rqos-&amp;gt;ops-&amp;gt;exit(rqos);
      wbt_exit()&lt;/p&gt;
&lt;p&gt;So rq_qos_exit() is called to free the rq_wb memory for wbt_init().
However in the error path of device_add_disk(), only
blk_unregister_queue() is called and make rq_wb memory leaked.&lt;/p&gt;
&lt;p&gt;Add rq_qos_exit() to the error path to fix it.&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;block: Fix possible memory leak for rq_wb on add_disk failure&lt;/p&gt;
&lt;p&gt;kmemleak reported memory leaks in device_add_disk():&lt;/p&gt;
&lt;p&gt;kmemleak: 3 new suspected memory leaks&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88800f420800 (size 512):
  comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)
  hex dump (first 32 bytes):
    04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................
    00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60
    [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0
    [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0
    [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420
    [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40
    [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]
    ...&lt;/p&gt;
&lt;p&gt;It is because the memory allocated in wbt_enable_default() is not
released in device_add_disk() error path.
Normally, these memory are freed in:&lt;/p&gt;
&lt;p&gt;del_gendisk()
  rq_qos_exit()
    rqos-&amp;gt;ops-&amp;gt;exit(rqos);
      wbt_exit()&lt;/p&gt;
&lt;p&gt;So rq_qos_exit() is called to free the rq_wb memory for wbt_init().
However in the error path of device_add_disk(), only
blk_unregister_queue() is called and make rq_wb memory leaked.&lt;/p&gt;
&lt;p&gt;Add rq_qos_exit() to the error path to fix it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49902</guid>
    </item>
    <item>
      <title>GHSA-8p4q-63f6-rqfp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8p4q-63f6-rqfp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: Fix possible memory leak for rq_wb on add_disk failure&lt;/p&gt;
&lt;p&gt;kmemleak reported memory leaks in device_add_disk():&lt;/p&gt;
&lt;p&gt;kmemleak: 3 new suspected memory leaks&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88800f420800 (size 512):
  comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)
  hex dump (first 32 bytes):
    04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................
    00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60
    [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0
    [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0
    [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420
    [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40
    [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]
    ...&lt;/p&gt;
&lt;p&gt;It is because the memory allocated in wbt_enable_default() is not
released in device_add_disk() error path.
Normally, these memory are freed in:&lt;/p&gt;
&lt;p&gt;del_gendisk()
  rq_qos_exit()
    rqos-&amp;gt;ops-&amp;gt;exit(rqos);
      wbt_exit()&lt;/p&gt;
&lt;p&gt;So rq_qos_exit() is called to free the rq_wb memory for wbt_init().
However in the error path of device_add_disk(), only
blk_unregister_queue() is called and make rq_wb memory leaked.&lt;/p&gt;
&lt;p&gt;Add rq_qos_exit() to the error path to fix it.&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;block: Fix possible memory leak for rq_wb on add_disk failure&lt;/p&gt;
&lt;p&gt;kmemleak reported memory leaks in device_add_disk():&lt;/p&gt;
&lt;p&gt;kmemleak: 3 new suspected memory leaks&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88800f420800 (size 512):
  comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)
  hex dump (first 32 bytes):
    04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................
    00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60
    [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0
    [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0
    [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420
    [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40
    [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]
    ...&lt;/p&gt;
&lt;p&gt;It is because the memory allocated in wbt_enable_default() is not
released in device_add_disk() error path.
Normally, these memory are freed in:&lt;/p&gt;
&lt;p&gt;del_gendisk()
  rq_qos_exit()
    rqos-&amp;gt;ops-&amp;gt;exit(rqos);
      wbt_exit()&lt;/p&gt;
&lt;p&gt;So rq_qos_exit() is called to free the rq_wb memory for wbt_init().
However in the error path of device_add_disk(), only
blk_unregister_queue() is called and make rq_wb memory leaked.&lt;/p&gt;
&lt;p&gt;Add rq_qos_exit() to the error path to fix it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8p4q-63f6-rqfp</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2458</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-49902</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49902</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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: block: Fix possible memory leak for rq_wb on add_disk failure kmemleak reported memory leaks in device_add_disk(): kmemleak: 3 new suspected memory leaks unreferenced object 0xffff88800f420800 (size 512):   comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)   hex dump (first 32 bytes):     04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................     00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60     [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0     [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0     [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420     [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40     [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]     ... It is because the memory allocated in wbt_enable_default() is not released in device_add_disk() error path. Normally, these memory are freed in: del_gendisk()   rq_qos_exit()     rqos-&amp;gt;ops-&amp;gt;exit(rqos);       wbt_exit() So rq_qos_exit() is called to free the rq_wb memory for wbt_init(). However in the error path of device_add_disk(), only blk_unregister_queue() is called and make rq_wb memory leaked. Add rq_qos_exit() to the error path to fix it.&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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: block: Fix possible memory leak for rq_wb on add_disk failure kmemleak reported memory leaks in device_add_disk(): kmemleak: 3 new suspected memory leaks unreferenced object 0xffff88800f420800 (size 512):   comm &amp;#34;modprobe&amp;#34;, pid 4275, jiffies 4295639067 (age 223.512s)   hex dump (first 32 bytes):     04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00  ................     00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&amp;lt;00000000d3662699&amp;gt;] kmalloc_trace+0x26/0x60     [&amp;lt;00000000edc7aadc&amp;gt;] wbt_init+0x50/0x6f0     [&amp;lt;0000000069601d16&amp;gt;] wbt_enable_default+0x157/0x1c0     [&amp;lt;0000000028fc393f&amp;gt;] blk_register_queue+0x2a4/0x420     [&amp;lt;000000007345a042&amp;gt;] device_add_disk+0x6fd/0xe40     [&amp;lt;0000000060e6aab0&amp;gt;] nbd_dev_add+0x828/0xbf0 [nbd]     ... It is because the memory allocated in wbt_enable_default() is not released in device_add_disk() error path. Normally, these memory are freed in: del_gendisk()   rq_qos_exit()     rqos-&amp;gt;ops-&amp;gt;exit(rqos);       wbt_exit() So rq_qos_exit() is called to free the rq_wb memory for wbt_init(). However in the error path of device_add_disk(), only blk_unregister_queue() is called and make rq_wb memory leaked. Add rq_qos_exit() to the error path to fix it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49902</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>
