<?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 22:25:41 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:6997 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:6997</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: uio: Fix use-after-free in uio_open (CVE-2023-52439)
  * kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb (CVE-2024-26739)
  * kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses (CVE-2024-26947)
  * kernel: scsi: qla2xxx: Fix command flush on cable pull (CVE-2024-26931)
  * kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer (CVE-2024-26930)
  * kernel: scsi: qla2xxx: Fix double free of fcport (CVE-2024-26929)
  * kernel: fork: defer linking file vma until vma is fully initialized (CVE-2024-27022)
  * kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes (CVE-2024-26991)
  * kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem (CVE-2024-35895)
  * kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (CVE-2024-36016)
  * kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (CVE-2024-36899)
  * kernel: cpufreq: exit() callback is optional (CVE-2024-38615)
  * kernel: ring-buffer: Fix a race between readers and resize checks (CVE-2024-38601)
  * kernel: cppc_cpufreq: Fix possible null pointer dereference (CVE-2024-38573)
  * kernel: gfs2: Fix potential glock use-after-free on unmount (CVE-2024-38570)
  * kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing (CVE-2024-38562)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: uio: Fix use-after-free in uio_open (CVE-2023-52439)
  * kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb (CVE-2024-26739)
  * kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses (CVE-2024-26947)
  * kernel: scsi: qla2xxx: Fix command flush on cable pull (CVE-2024-26931)
  * kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer (CVE-2024-26930)
  * kernel: scsi: qla2xxx: Fix double free of fcport (CVE-2024-26929)
  * kernel: fork: defer linking file vma until vma is fully initialized (CVE-2024-27022)
  * kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes (CVE-2024-26991)
  * kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem (CVE-2024-35895)
  * kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (CVE-2024-36016)
  * kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (CVE-2024-36899)
  * kernel: cpufreq: exit() callback is optional (CVE-2024-38615)
  * kernel: ring-buffer: Fix a race between readers and resize checks (CVE-2024-38601)
  * kernel: cppc_cpufreq: Fix possible null pointer dereference (CVE-2024-38573)
  * kernel: gfs2: Fix potential glock use-after-free on unmount (CVE-2024-38570)
  * kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing (CVE-2024-38562)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:6997</guid>
    </item>
    <item>
      <title>bdu:2025-01420</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01420</link>
      <description>bdu:2025-01420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01420</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-42246</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-42246</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-42246</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>EUVD-2026-313087</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313087</link>
      <description>EUVD-2026-313087</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313087</guid>
    </item>
    <item>
      <title>fkie_cve-2024-42246</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-42246</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;
&lt;p&gt;When using a BPF program on kernel_connect(), the call can return -EPERM. This
causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing
the kernel to potentially freeze up.&lt;/p&gt;
&lt;p&gt;Neil suggested:&lt;/p&gt;
&lt;p&gt;This will propagate -EPERM up into other layers which might not be ready
  to handle it. It might be safer to map EPERM to an error we would be more
  likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.&lt;/p&gt;
&lt;p&gt;ECONNREFUSED as error seems reasonable. For programs setting a different error
can be out of reach (see handling in 4fbac77d2d09) in particular on kernels
which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err
instead of allow boolean&amp;#34;), thus given that it is better to simply remap for
consistent behavior. UDP does handle EPERM in xs_udp_send_request().&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;net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;
&lt;p&gt;When using a BPF program on kernel_connect(), the call can return -EPERM. This
causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing
the kernel to potentially freeze up.&lt;/p&gt;
&lt;p&gt;Neil suggested:&lt;/p&gt;
&lt;p&gt;This will propagate -EPERM up into other layers which might not be ready
  to handle it. It might be safer to map EPERM to an error we would be more
  likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.&lt;/p&gt;
&lt;p&gt;ECONNREFUSED as error seems reasonable. For programs setting a different error
can be out of reach (see handling in 4fbac77d2d09) in particular on kernels
which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err
instead of allow boolean&amp;#34;), thus given that it is better to simply remap for
consistent behavior. UDP does handle EPERM in xs_udp_send_request().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-42246</guid>
    </item>
    <item>
      <title>GHSA-899c-qvc8-9hpp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-899c-qvc8-9hpp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;
&lt;p&gt;When using a BPF program on kernel_connect(), the call can return -EPERM. This
causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing
the kernel to potentially freeze up.&lt;/p&gt;
&lt;p&gt;Neil suggested:&lt;/p&gt;
&lt;p&gt;This will propagate -EPERM up into other layers which might not be ready
  to handle it. It might be safer to map EPERM to an error we would be more
  likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.&lt;/p&gt;
&lt;p&gt;ECONNREFUSED as error seems reasonable. For programs setting a different error
can be out of reach (see handling in 4fbac77d2d09) in particular on kernels
which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err
instead of allow boolean&amp;#34;), thus given that it is better to simply remap for
consistent behavior. UDP does handle EPERM in xs_udp_send_request().&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;net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;
&lt;p&gt;When using a BPF program on kernel_connect(), the call can return -EPERM. This
causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing
the kernel to potentially freeze up.&lt;/p&gt;
&lt;p&gt;Neil suggested:&lt;/p&gt;
&lt;p&gt;This will propagate -EPERM up into other layers which might not be ready
  to handle it. It might be safer to map EPERM to an error we would be more
  likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.&lt;/p&gt;
&lt;p&gt;ECONNREFUSED as error seems reasonable. For programs setting a different error
can be out of reach (see handling in 4fbac77d2d09) in particular on kernels
which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err
instead of allow boolean&amp;#34;), thus given that it is better to simply remap for
consistent behavior. UDP does handle EPERM in xs_udp_send_request().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-899c-qvc8-9hpp</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-42246 — net sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-42246</link>
      <description>msrc_CVE-2024-42246</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-42246</guid>
    </item>
    <item>
      <title>OESA-2024-1992 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1992</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;
USB: core: Make do_proc_control() and do_proc_bulk() killable&#13;
&#13;
The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke
usb_start_wait_urb(), which contains an uninterruptible wait with a
user-specified timeout value.  If timeout value is very large and the
device being accessed does not respond in a reasonable amount of time,
the kernel will complain about &amp;amp;quot;Task X blocked for more than N
seconds&amp;amp;quot;, as found in testing by syzbot:&#13;
&#13;
INFO: task syz-executor.0:8700 blocked for more than 143 seconds.
      Not tainted 5.14.0-rc7-syzkaller #0
&amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
task:syz-executor.0  state:D stack:23192 pid: 8700 ppid:  8455 flags:0x00004004
Call Trace:
 context_switch kernel/sched/core.c:4681 [inline]
 __schedule+0xc07/0x11f0 kernel/sched/core.c:5938
 schedule+0x14b/0x210 kernel/sched/core.c:6017
 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857
 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157
 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63
 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236
 proc_bulk drivers/usb/core/devio.c:1273 [inline]
 usbdev…&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;
USB: core: Make do_proc_control() and do_proc_bulk() killable&#13;
&#13;
The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke
usb_start_wait_urb(), which contains an uninterruptible wait with a
user-specified timeout value.  If timeout value is very large and the
device being accessed does not respond in a reasonable amount of time,
the kernel will complain about &amp;amp;quot;Task X blocked for more than N
seconds&amp;amp;quot;, as found in testing by syzbot:&#13;
&#13;
INFO: task syz-executor.0:8700 blocked for more than 143 seconds.
      Not tainted 5.14.0-rc7-syzkaller #0
&amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
task:syz-executor.0  state:D stack:23192 pid: 8700 ppid:  8455 flags:0x00004004
Call Trace:
 context_switch kernel/sched/core.c:4681 [inline]
 __schedule+0xc07/0x11f0 kernel/sched/core.c:5938
 schedule+0x14b/0x210 kernel/sched/core.c:6017
 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857
 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157
 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63
 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236
 proc_bulk drivers/usb/core/devio.c:1273 [inline]
 usbdev…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1992</guid>
    </item>
    <item>
      <title>RHSA-2024:6744 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:6744</link>
      <description>&lt;p&gt;kernel: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc kernel: Bluetooth: af_bluetooth: Fix deadlock kernel: crypto: qat - resolve race condition during AER recovery kernel: scsi: qedf: Ensure the copied buf is NUL terminated kernel: cppc_cpufreq: Fix possible null pointer dereference kernel: cpufreq: exit() callback is optional kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: sched/deadline: Fix task_struct reference leak kernel: mm/filemap: skip to create PMD-sized page cache if needed kernel: mm/shmem: disable PMD-sized page cache if needed kernel: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray kernel: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc kernel: Bluetooth: af_bluetooth: Fix deadlock kernel: crypto: qat - resolve race condition during AER recovery kernel: scsi: qedf: Ensure the copied buf is NUL terminated kernel: cppc_cpufreq: Fix possible null pointer dereference kernel: cpufreq: exit() callback is optional kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: sched/deadline: Fix task_struct reference leak kernel: mm/filemap: skip to create PMD-sized page cache if needed kernel: mm/shmem: disable PMD-sized page cache if needed kernel: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray kernel: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:6744</guid>
    </item>
    <item>
      <title>RHSA-2024:6997 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:6997</link>
      <description>&lt;p&gt;kernel: uio: Fix use-after-free in uio_open kernel: Input: cyapa - add missing input core locking to suspend/resume functions kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb kernel: scsi: qla2xxx: Fix double free of fcport kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer kernel: scsi: qla2xxx: Fix command flush on cable pull kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes kernel: fork: defer linking file vma until vma is fully initialized kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing kernel: gfs2: Fix potential glock use-after-free on unmount kernel: cppc_cpufreq: Fix possible null pointer dereference kernel: ring-buffer: Fix a race between readers and resize checks kernel: cpufreq: exit() callback is optional kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: wifi: mac80211: Avoid address calculations via out of bounds array indexing kernel: wifi: mt76: replace skb_put with skb_put_zero kernel: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: uio: Fix use-after-free in uio_open kernel: Input: cyapa - add missing input core locking to suspend/resume functions kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb kernel: scsi: qla2xxx: Fix double free of fcport kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer kernel: scsi: qla2xxx: Fix command flush on cable pull kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes kernel: fork: defer linking file vma until vma is fully initialized kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing kernel: gfs2: Fix potential glock use-after-free on unmount kernel: cppc_cpufreq: Fix possible null pointer dereference kernel: ring-buffer: Fix a race between readers and resize checks kernel: cpufreq: exit() callback is optional kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: wifi: mac80211: Avoid address calculations via out of bounds array indexing kernel: wifi: mt76: replace skb_put with skb_put_zero kernel: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:6997</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3189-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3189-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:3189-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-42246</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42246</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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket When using a BPF program on kernel_connect(), the call can return -EPERM. This causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing the kernel to potentially freeze up. Neil suggested:   This will propagate -EPERM up into other layers which might not be ready   to handle it. It might be safer to map EPERM to an error we would be more   likely to expect from the network system - such as ECONNREFUSED or ENETDOWN. ECONNREFUSED as error seems reasonable. For programs setting a different error can be out of reach (see handling in 4fbac77d2d09) in particular on kernels which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err instead of allow boolean&amp;#34;), thus given that it is better to simply remap for consistent behavior. UDP does handle EPERM in xs_udp_send_request().&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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket When using a BPF program on kernel_connect(), the call can return -EPERM. This causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing the kernel to potentially freeze up. Neil suggested:   This will propagate -EPERM up into other layers which might not be ready   to handle it. It might be safer to map EPERM to an error we would be more   likely to expect from the network system - such as ECONNREFUSED or ENETDOWN. ECONNREFUSED as error seems reasonable. For programs setting a different error can be out of reach (see handling in 4fbac77d2d09) in particular on kernels which do not have f10d05966196 (&amp;#34;bpf: Make BPF_PROG_RUN_ARRAY return -err instead of allow boolean&amp;#34;), thus given that it is better to simply remap for consistent behavior. UDP does handle EPERM in xs_udp_send_request().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42246</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1788 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1788</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1788</guid>
    </item>
  </channel>
</rss>
