<?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 15:52:43 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:63013 — Important: kernel-rt security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:63013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling (CVE-2024-57849)
  * kernel: smc91x: fix broken irq-context in PREEMPT_RT (CVE-2025-71132)
  * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)
  * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)
  * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)
  * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)
  * kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)
  * kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access (CVE-2026-64018)
  * kernel: Kernel: Remote out-of-bounds write in RDMA/siw (CVE-2026-64268)
  * kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (CVE-2026-64298)
  * kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability (CVE-2026-68480)
  * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* qede: build_skb failure causes off-by-one BD ring corruption and kernel panic [almalinux-8.10.z] (JIRA:AlmaL…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling (CVE-2024-57849)
  * kernel: smc91x: fix broken irq-context in PREEMPT_RT (CVE-2025-71132)
  * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)
  * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)
  * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)
  * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)
  * kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)
  * kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access (CVE-2026-64018)
  * kernel: Kernel: Remote out-of-bounds write in RDMA/siw (CVE-2026-64268)
  * kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (CVE-2026-64298)
  * kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability (CVE-2026-68480)
  * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* qede: build_skb failure causes off-by-one BD ring corruption and kernel panic [almalinux-8.10.z] (JIRA:AlmaL…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:63013</guid>
    </item>
    <item>
      <title>bdu:2026-10906</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10906</link>
      <description>bdu:2026-10906</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10906</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71132</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71132</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-2025-71132</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-347554</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347554</link>
      <description>EUVD-2026-347554</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347554</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71132</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71132</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smc91x: fix broken irq-context in PREEMPT_RT&lt;/p&gt;
&lt;p&gt;When smc91x.c is built with PREEMPT_RT, the following splat occurs
in FVP_RevC:&lt;/p&gt;
&lt;p&gt;[   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000
[   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106]
[   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work
[   13.062266] C
** replaying previous printk message **
[   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)}
[   13.062353] Hardware name:  , BIOS
[   13.062382] Workqueue: mld mld_ifc_work
[   13.062469] Call trace:
[   13.062494]  show_stack+0x24/0x40 (C)
[   13.062602]  __dump_stack+0x28/0x48
[   13.062710]  dump_stack_lvl+0x7c/0xb0
[   13.062818]  dump_stack+0x18/0x34
[   13.062926]  process_scheduled_works+0x294/0x450
[   13.063043]  worker_thread+0x260/0x3d8
[   13.063124]  kthread+0x1c4/0x228
[   13.063235]  ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT,
but smc_special_unlock() does not restore IRQs on PREEMPT_RT.
The reason is that smc_special_unlock() calls spin_unlock_irqrestore(),
and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke
rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero.&lt;/p&gt;
&lt;p&gt;To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&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;smc91x: fix broken irq-context in PREEMPT_RT&lt;/p&gt;
&lt;p&gt;When smc91x.c is built with PREEMPT_RT, the following splat occurs
in FVP_RevC:&lt;/p&gt;
&lt;p&gt;[   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000
[   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106]
[   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work
[   13.062266] C
** replaying previous printk message **
[   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)}
[   13.062353] Hardware name:  , BIOS
[   13.062382] Workqueue: mld mld_ifc_work
[   13.062469] Call trace:
[   13.062494]  show_stack+0x24/0x40 (C)
[   13.062602]  __dump_stack+0x28/0x48
[   13.062710]  dump_stack_lvl+0x7c/0xb0
[   13.062818]  dump_stack+0x18/0x34
[   13.062926]  process_scheduled_works+0x294/0x450
[   13.063043]  worker_thread+0x260/0x3d8
[   13.063124]  kthread+0x1c4/0x228
[   13.063235]  ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT,
but smc_special_unlock() does not restore IRQs on PREEMPT_RT.
The reason is that smc_special_unlock() calls spin_unlock_irqrestore(),
and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke
rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero.&lt;/p&gt;
&lt;p&gt;To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71132</guid>
    </item>
    <item>
      <title>GHSA-52xq-4j7g-g3fj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-52xq-4j7g-g3fj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smc91x: fix broken irq-context in PREEMPT_RT&lt;/p&gt;
&lt;p&gt;When smc91x.c is built with PREEMPT_RT, the following splat occurs
in FVP_RevC:&lt;/p&gt;
&lt;p&gt;[   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000
[   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106]
[   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work
[   13.062266] C
** replaying previous printk message **
[   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)}
[   13.062353] Hardware name:  , BIOS
[   13.062382] Workqueue: mld mld_ifc_work
[   13.062469] Call trace:
[   13.062494]  show_stack+0x24/0x40 (C)
[   13.062602]  __dump_stack+0x28/0x48
[   13.062710]  dump_stack_lvl+0x7c/0xb0
[   13.062818]  dump_stack+0x18/0x34
[   13.062926]  process_scheduled_works+0x294/0x450
[   13.063043]  worker_thread+0x260/0x3d8
[   13.063124]  kthread+0x1c4/0x228
[   13.063235]  ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT,
but smc_special_unlock() does not restore IRQs on PREEMPT_RT.
The reason is that smc_special_unlock() calls spin_unlock_irqrestore(),
and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke
rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero.&lt;/p&gt;
&lt;p&gt;To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&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;smc91x: fix broken irq-context in PREEMPT_RT&lt;/p&gt;
&lt;p&gt;When smc91x.c is built with PREEMPT_RT, the following splat occurs
in FVP_RevC:&lt;/p&gt;
&lt;p&gt;[   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000
[   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106]
[   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work
[   13.062266] C
** replaying previous printk message **
[   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)}
[   13.062353] Hardware name:  , BIOS
[   13.062382] Workqueue: mld mld_ifc_work
[   13.062469] Call trace:
[   13.062494]  show_stack+0x24/0x40 (C)
[   13.062602]  __dump_stack+0x28/0x48
[   13.062710]  dump_stack_lvl+0x7c/0xb0
[   13.062818]  dump_stack+0x18/0x34
[   13.062926]  process_scheduled_works+0x294/0x450
[   13.063043]  worker_thread+0x260/0x3d8
[   13.063124]  kthread+0x1c4/0x228
[   13.063235]  ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT,
but smc_special_unlock() does not restore IRQs on PREEMPT_RT.
The reason is that smc_special_unlock() calls spin_unlock_irqrestore(),
and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke
rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero.&lt;/p&gt;
&lt;p&gt;To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-52xq-4j7g-g3fj</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-71132 — smc91x: fix broken irq-context in PREEMPT_RT</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-71132</link>
      <description>msrc_CVE-2025-71132</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-71132</guid>
    </item>
    <item>
      <title>OESA-2026-2581 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2581</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;net: mvpp2: Prevent parser TCAM memory corruption&lt;/p&gt;
&lt;p&gt;Protect the parser TCAM/SRAM memory, and the cached (shadow) SRAM
information, from concurrent modifications.&lt;/p&gt;
&lt;p&gt;Both the TCAM and SRAM tables are indirectly accessed by configuring
an index register that selects the row to read or write to. This means
that operations must be atomic in order to, e.g., avoid spreading
writes across multiple rows. Since the shadow SRAM array is used to
find free rows in the hardware table, it must also be protected in
order to avoid TOCTOU errors where multiple cores allocate the same
row.&lt;/p&gt;
&lt;p&gt;This issue was detected in a situation where `mvpp2_set_rx_mode()` ran
concurrently on two CPUs. In this particular case the
MVPP2_PE_MAC_UC_PROMISCUOUS entry was corrupted, causing the
classifier unit to drop all incoming unicast - indicated by the
`rx_classifier_drops` counter.(CVE-2025-22060)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: fix NULL pointer in can_accept_new_subflow&lt;/p&gt;
&lt;p&gt;When testing valkey benchmark tool with MPTCP, the kernel panics in
&amp;amp;apos;mptcp_can_accept_new_subflow&amp;amp;apos; because subflow_req-&amp;amp;gt;msk is NULL.&lt;/p&gt;
&lt;p&gt;Call trace:&lt;/p&gt;
&lt;p&gt;mptcp_can_accept_new_subflow (./net/mptcp/subflow.c:63 (discriminator 4)) (P)
  subflow_syn_recv_sock (./net/mptcp/subflow.c:854)
  tcp_check_req (./net/ipv4/tcp_minisocks.c:863)
  tcp_v4_rcv (./net/…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;net: mvpp2: Prevent parser TCAM memory corruption&lt;/p&gt;
&lt;p&gt;Protect the parser TCAM/SRAM memory, and the cached (shadow) SRAM
information, from concurrent modifications.&lt;/p&gt;
&lt;p&gt;Both the TCAM and SRAM tables are indirectly accessed by configuring
an index register that selects the row to read or write to. This means
that operations must be atomic in order to, e.g., avoid spreading
writes across multiple rows. Since the shadow SRAM array is used to
find free rows in the hardware table, it must also be protected in
order to avoid TOCTOU errors where multiple cores allocate the same
row.&lt;/p&gt;
&lt;p&gt;This issue was detected in a situation where `mvpp2_set_rx_mode()` ran
concurrently on two CPUs. In this particular case the
MVPP2_PE_MAC_UC_PROMISCUOUS entry was corrupted, causing the
classifier unit to drop all incoming unicast - indicated by the
`rx_classifier_drops` counter.(CVE-2025-22060)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mptcp: fix NULL pointer in can_accept_new_subflow&lt;/p&gt;
&lt;p&gt;When testing valkey benchmark tool with MPTCP, the kernel panics in
&amp;amp;apos;mptcp_can_accept_new_subflow&amp;amp;apos; because subflow_req-&amp;amp;gt;msk is NULL.&lt;/p&gt;
&lt;p&gt;Call trace:&lt;/p&gt;
&lt;p&gt;mptcp_can_accept_new_subflow (./net/mptcp/subflow.c:63 (discriminator 4)) (P)
  subflow_syn_recv_sock (./net/mptcp/subflow.c:854)
  tcp_check_req (./net/ipv4/tcp_minisocks.c:863)
  tcp_v4_rcv (./net/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2581</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20287-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20287-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/opensuse-su-2026:20287-1</guid>
    </item>
    <item>
      <title>RHSA-2026:63013 — Red Hat Security Advisory: kernel-rt security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:63013</link>
      <description>&lt;p&gt;kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling kernel: smc91x: fix broken irq-context in PREEMPT_RT kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down kernel: zram: fix use-after-free in zram_bvec_write_partial() kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr kernel: NFSv4/flexfiles: reject zero filehandle version count kernel: nfsd: fix posix_acl leak on SETACL decode failure kernel: nfsd: release layout stid on setlease failure kernel: pNFS: Fix use-after-free in pnfs_update_layout() kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access kernel: Kernel: Remote out-of-bounds write in RDMA/siw kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling kernel: smc91x: fix broken irq-context in PREEMPT_RT kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down kernel: zram: fix use-after-free in zram_bvec_write_partial() kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr kernel: NFSv4/flexfiles: reject zero filehandle version count kernel: nfsd: fix posix_acl leak on SETACL decode failure kernel: nfsd: release layout stid on setlease failure kernel: pNFS: Fix use-after-free in pnfs_update_layout() kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access kernel: Kernel: Remote out-of-bounds write in RDMA/siw kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:63013</guid>
    </item>
    <item>
      <title>RLSA-2026:63013 — Important: kernel-rt security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:63013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling (CVE-2024-57849)&lt;/p&gt;
&lt;p&gt;* kernel: smc91x: fix broken irq-context in PREEMPT_RT (CVE-2025-71132)&lt;/p&gt;
&lt;p&gt;* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)&lt;/p&gt;
&lt;p&gt;* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)&lt;/p&gt;
&lt;p&gt;* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)&lt;/p&gt;
&lt;p&gt;* kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access (CVE-2026-64018)&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Remote out-of-bounds write in RDMA/siw (CVE-2026-64268)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (CVE-2026-64298)&lt;/p&gt;
&lt;p&gt;* kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability (CVE-2026-68480)&lt;/p&gt;
&lt;p&gt;* kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* qede: build_skb failure causes off-by-one BD ring corruption and kernel panic [rhel-8.10.z] (JIRA:Rocky Linux-193045)&lt;/p&gt;
&lt;p&gt;* powerpc/pse…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: s390/cpum_sf: Handle CPU hotplug remove during sampling (CVE-2024-57849)&lt;/p&gt;
&lt;p&gt;* kernel: smc91x: fix broken irq-context in PREEMPT_RT (CVE-2025-71132)&lt;/p&gt;
&lt;p&gt;* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)&lt;/p&gt;
&lt;p&gt;* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)&lt;/p&gt;
&lt;p&gt;* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)&lt;/p&gt;
&lt;p&gt;* kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access (CVE-2026-64018)&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Remote out-of-bounds write in RDMA/siw (CVE-2026-64268)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (CVE-2026-64298)&lt;/p&gt;
&lt;p&gt;* kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability (CVE-2026-68480)&lt;/p&gt;
&lt;p&gt;* kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* qede: build_skb failure causes off-by-one BD ring corruption and kernel panic [rhel-8.10.z] (JIRA:Rocky Linux-193045)&lt;/p&gt;
&lt;p&gt;* powerpc/pse…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:63013</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0587-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0587-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-2026:0587-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71132</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71132</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 178 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smc91x: fix broken irq-context in PREEMPT_RT When smc91x.c is built with PREEMPT_RT, the following splat occurs in FVP_RevC: [   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000 [   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106] [   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work [   13.062266] C ** replaying previous printk message ** [   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)} [   13.062353] Hardware name:  , BIOS [   13.062382] Workqueue: mld mld_ifc_work [   13.062469] Call trace: [   13.062494]  show_stack+0x24/0x40 (C) [   13.062602]  __dump_stack+0x28/0x48 [   13.062710]  dump_stack_lvl+0x7c/0xb0 [   13.062818]  dump_stack+0x18/0x34 [   13.062926]  process_scheduled_works+0x294/0x450 [   13.063043]  worker_thread+0x260/0x3d8 [   13.063124]  kthread+0x1c4/0x228 [   13.063235]  ret_from_fork+0x10/0x20 This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT, but smc_special_unlock() does not restore IRQs on PREEMPT_RT. The reason is that smc_special_unlock() calls spin_unlock_irqrestore(), and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero. To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&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 178 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smc91x: fix broken irq-context in PREEMPT_RT When smc91x.c is built with PREEMPT_RT, the following splat occurs in FVP_RevC: [   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000 [   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106] [   13.062137]      preempt=0x00000000 lock=0-&amp;gt;0 RCU=0-&amp;gt;1 workfn=mld_ifc_work [   13.062266] C ** replaying previous printk message ** [   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)} [   13.062353] Hardware name:  , BIOS [   13.062382] Workqueue: mld mld_ifc_work [   13.062469] Call trace: [   13.062494]  show_stack+0x24/0x40 (C) [   13.062602]  __dump_stack+0x28/0x48 [   13.062710]  dump_stack_lvl+0x7c/0xb0 [   13.062818]  dump_stack+0x18/0x34 [   13.062926]  process_scheduled_works+0x294/0x450 [   13.063043]  worker_thread+0x260/0x3d8 [   13.063124]  kthread+0x1c4/0x228 [   13.063235]  ret_from_fork+0x10/0x20 This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT, but smc_special_unlock() does not restore IRQs on PREEMPT_RT. The reason is that smc_special_unlock() calls spin_unlock_irqrestore(), and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke rcu_read_unlock() through __local_bh_enable_ip() when current-&amp;gt;softirq_disable_cnt becomes zero. To address this issue, replace smc_special_trylock() with spin_trylock_irqsave().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71132</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</guid>
    </item>
  </channel>
</rss>
