<?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 21:17:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04458</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04458</link>
      <description>bdu:2025-04458</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04458</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-309807</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309807</link>
      <description>EUVD-2026-309807</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309807</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47556</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47556</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()&lt;/p&gt;
&lt;p&gt;ethtool_set_coalesce() now uses both the .get_coalesce() and
.set_coalesce() callbacks. But the check for their availability is
buggy, so changing the coalesce settings on a device where the driver
provides only _one_ of the callbacks results in a NULL pointer
dereference instead of an -EOPNOTSUPP.&lt;/p&gt;
&lt;p&gt;Fix the condition so that the availability of both callbacks is
ensured. This also matches the netlink code.&lt;/p&gt;
&lt;p&gt;Note that reproducing this requires some effort - it only affects the
legacy ioctl path, and needs a specific combination of driver options:
- have .get_coalesce() and .coalesce_supported but no
 .set_coalesce(), or
- have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t
  cause the crash as it first attempts to call ethtool_get_coalesce()
  and bails out on error.&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;ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()&lt;/p&gt;
&lt;p&gt;ethtool_set_coalesce() now uses both the .get_coalesce() and
.set_coalesce() callbacks. But the check for their availability is
buggy, so changing the coalesce settings on a device where the driver
provides only _one_ of the callbacks results in a NULL pointer
dereference instead of an -EOPNOTSUPP.&lt;/p&gt;
&lt;p&gt;Fix the condition so that the availability of both callbacks is
ensured. This also matches the netlink code.&lt;/p&gt;
&lt;p&gt;Note that reproducing this requires some effort - it only affects the
legacy ioctl path, and needs a specific combination of driver options:
- have .get_coalesce() and .coalesce_supported but no
 .set_coalesce(), or
- have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t
  cause the crash as it first attempts to call ethtool_get_coalesce()
  and bails out on error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47556</guid>
    </item>
    <item>
      <title>OESA-2024-2080 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2080</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
io_uring: fix memleak in io_init_wq_offload()&#13;
&#13;
I got memory leak report when doing fuzz test:&#13;
&#13;
BUG: memory leak
unreferenced object 0xffff888107310a80 (size 96):
comm &amp;amp;quot;syz-executor.6&amp;amp;quot;, pid 4610, jiffies 4295140240 (age 20.135s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
backtrace:
[&amp;amp;lt;000000001974933b&amp;amp;gt;] kmalloc include/linux/slab.h:591 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] kzalloc include/linux/slab.h:721 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] io_init_wq_offload fs/io_uring.c:7920 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] io_uring_alloc_task_context+0x466/0x640 fs/io_uring.c:7955
[&amp;amp;lt;0000000039d0800d&amp;amp;gt;] __io_uring_add_tctx_node+0x256/0x360 fs/io_uring.c:9016
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] io_uring_add_tctx_node fs/io_uring.c:9052 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __do_sys_io_uring_enter fs/io_uring.c:9354 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __se_sys_io_uring_enter fs/io_uring.c:9301 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __x64_sys_io_uring_enter+0xabc/0xc20 fs/io_uring.c:9301
[&amp;amp;lt;00000000b875f18f&amp;amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[&amp;amp;lt;00000000b875f18f&amp;amp;gt;] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80
[&amp;amp;lt;000000006b0a8484&amp;amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&#13;
&#13;
CPU0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
io_uring: fix memleak in io_init_wq_offload()&#13;
&#13;
I got memory leak report when doing fuzz test:&#13;
&#13;
BUG: memory leak
unreferenced object 0xffff888107310a80 (size 96):
comm &amp;amp;quot;syz-executor.6&amp;amp;quot;, pid 4610, jiffies 4295140240 (age 20.135s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
backtrace:
[&amp;amp;lt;000000001974933b&amp;amp;gt;] kmalloc include/linux/slab.h:591 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] kzalloc include/linux/slab.h:721 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] io_init_wq_offload fs/io_uring.c:7920 [inline]
[&amp;amp;lt;000000001974933b&amp;amp;gt;] io_uring_alloc_task_context+0x466/0x640 fs/io_uring.c:7955
[&amp;amp;lt;0000000039d0800d&amp;amp;gt;] __io_uring_add_tctx_node+0x256/0x360 fs/io_uring.c:9016
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] io_uring_add_tctx_node fs/io_uring.c:9052 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __do_sys_io_uring_enter fs/io_uring.c:9354 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __se_sys_io_uring_enter fs/io_uring.c:9301 [inline]
[&amp;amp;lt;000000008482e78c&amp;amp;gt;] __x64_sys_io_uring_enter+0xabc/0xc20 fs/io_uring.c:9301
[&amp;amp;lt;00000000b875f18f&amp;amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[&amp;amp;lt;00000000b875f18f&amp;amp;gt;] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80
[&amp;amp;lt;000000006b0a8484&amp;amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&#13;
&#13;
CPU0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2080</guid>
    </item>
    <item>
      <title>RHSA-2022:1975 — Red Hat Security Advisory: kernel-rt security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:1975</link>
      <description>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: new DNS Cache Poisoning Attack based on ICMP fragment needed packets…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: new DNS Cache Poisoning Attack based on ICMP fragment needed packets…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:1975</guid>
    </item>
    <item>
      <title>RHSA-2022:1988 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:1988</link>
      <description>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:1988</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-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-2024:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47556</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47556</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() ethtool_set_coalesce() now uses both the .get_coalesce() and .set_coalesce() callbacks. But the check for their availability is buggy, so changing the coalesce settings on a device where the driver provides only _one_ of the callbacks results in a NULL pointer dereference instead of an -EOPNOTSUPP. Fix the condition so that the availability of both callbacks is ensured. This also matches the netlink code. Note that reproducing this requires some effort - it only affects the legacy ioctl path, and needs a specific combination of driver options: - have .get_coalesce() and .coalesce_supported but no  .set_coalesce(), or - have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t   cause the crash as it first attempts to call ethtool_get_coalesce()   and bails out on error.&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() ethtool_set_coalesce() now uses both the .get_coalesce() and .set_coalesce() callbacks. But the check for their availability is buggy, so changing the coalesce settings on a device where the driver provides only _one_ of the callbacks results in a NULL pointer dereference instead of an -EOPNOTSUPP. Fix the condition so that the availability of both callbacks is ensured. This also matches the netlink code. Note that reproducing this requires some effort - it only affects the legacy ioctl path, and needs a specific combination of driver options: - have .get_coalesce() and .coalesce_supported but no  .set_coalesce(), or - have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t   cause the crash as it first attempts to call ethtool_get_coalesce()   and bails out on error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47556</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1235 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</guid>
    </item>
  </channel>
</rss>
