<?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 15:51:56 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:20095 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:20095</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
  * kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
  * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
  * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
  * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
  * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
  * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
  * kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
  * kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
  * kernel: io_uring/sqpoll: zero sqd-&amp;gt;thread on tctx errors (CVE-2025-21633)
  * kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
  * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
  * kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
  * kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
  * kernel: netfs: Fix ceph copy to cache…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
  * kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
  * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
  * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
  * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
  * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
  * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
  * kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
  * kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
  * kernel: io_uring/sqpoll: zero sqd-&amp;gt;thread on tctx errors (CVE-2025-21633)
  * kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
  * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
  * kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
  * kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
  * kernel: netfs: Fix ceph copy to cache…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:20095</guid>
    </item>
    <item>
      <title>bdu:2025-01800</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01800</link>
      <description>bdu:2025-01800</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01800</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21691</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-21691</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-21691</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0349 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0349</link>
      <description>certfr-2025-avi-0349</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0349</guid>
    </item>
    <item>
      <title>ESSA-2026:0153 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/essa-2026:0153</link>
      <description>&lt;p&gt;Important: kernel security, bug fix, and enhancement update&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Important: kernel security, bug fix, and enhancement update&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/essa-2026:0153</guid>
    </item>
    <item>
      <title>EUVD-2026-314010</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314010</link>
      <description>EUVD-2026-314010</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314010</guid>
    </item>
    <item>
      <title>fkie_cve-2025-21691</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21691</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cachestat: fix page cache statistics permission checking&lt;/p&gt;
&lt;p&gt;When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb
(&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much
more convenient (and performant) version of mincore() that didn&amp;#39;t need
mapping things into the user virtual address space in order to work.&lt;/p&gt;
&lt;p&gt;But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for
mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore()
more conservative&amp;#34;).&lt;/p&gt;
&lt;p&gt;This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file
context (rather than vma).&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;cachestat: fix page cache statistics permission checking&lt;/p&gt;
&lt;p&gt;When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb
(&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much
more convenient (and performant) version of mincore() that didn&amp;#39;t need
mapping things into the user virtual address space in order to work.&lt;/p&gt;
&lt;p&gt;But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for
mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore()
more conservative&amp;#34;).&lt;/p&gt;
&lt;p&gt;This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file
context (rather than vma).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-21691</guid>
    </item>
    <item>
      <title>GHSA-3m25-8xh3-c6p2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3m25-8xh3-c6p2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cachestat: fix page cache statistics permission checking&lt;/p&gt;
&lt;p&gt;When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb
(&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much
more convenient (and performant) version of mincore() that didn&amp;#39;t need
mapping things into the user virtual address space in order to work.&lt;/p&gt;
&lt;p&gt;But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for
mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore()
more conservative&amp;#34;).&lt;/p&gt;
&lt;p&gt;This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file
context (rather than vma).&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;cachestat: fix page cache statistics permission checking&lt;/p&gt;
&lt;p&gt;When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb
(&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much
more convenient (and performant) version of mincore() that didn&amp;#39;t need
mapping things into the user virtual address space in order to work.&lt;/p&gt;
&lt;p&gt;But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for
mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore()
more conservative&amp;#34;).&lt;/p&gt;
&lt;p&gt;This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file
context (rather than vma).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3m25-8xh3-c6p2</guid>
    </item>
    <item>
      <title>OESA-2025-1371 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1371</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;amp;quot;ovl: support
encoding non-decodable file handles&amp;amp;quot;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlayfs that is
mounted with options index=on,nfs_export=on also on kernels &amp;amp;lt; v6.6.
Therefore, I am not listing the aforementioned commit as a Fixes commit.&lt;/p&gt;
&lt;p&gt;Backport hint: this patch will have a trivial conflict applying to
v6.6.y, and other trivial conflicts applying to stable kernels &amp;amp;l…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;amp;quot;ovl: support
encoding non-decodable file handles&amp;amp;quot;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlayfs that is
mounted with options index=on,nfs_export=on also on kernels &amp;amp;lt; v6.6.
Therefore, I am not listing the aforementioned commit as a Fixes commit.&lt;/p&gt;
&lt;p&gt;Backport hint: this patch will have a trivial conflict applying to
v6.6.y, and other trivial conflicts applying to stable kernels &amp;amp;l…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1371</guid>
    </item>
    <item>
      <title>RHSA-2026:34094 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:34094</link>
      <description>&lt;p&gt;kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX kernel: cachestat: fix page cache statistics permission checking kernel: ALSA: aloop: Fix racy access at PCM trigger kernel: mptcp: fix slab-use-after-free in __inet_lookup_established kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup kernel: dlm: validate length in dlm_search_rsb_tree kernel: RDMA/umem: Fix double dma_buf_unpin in failure path kernel: tcp: fix potential race in tcp_v6_syn_recv_sock() kernel: netfilter: flowtable: strictly check for maximum number of actions kernel: scsi: qla2xxx: Completely fix fcport double free kernel: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows kernel: RDMA/rxe: Fix double free in rxe_srq_from_init kernel: ALSA: aloop: Fix peer runtime UAF during format-change stop kernel: exit: prevent preemption of oopsing TASK_DEAD task kernel: RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() kernel: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL kernel: netfilter: nft_inner: Fix IPv6 inner_thoff desync&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX kernel: cachestat: fix page cache statistics permission checking kernel: ALSA: aloop: Fix racy access at PCM trigger kernel: mptcp: fix slab-use-after-free in __inet_lookup_established kernel: netfilter: nf_conntrack_helper: pass helper to expect cleanup kernel: dlm: validate length in dlm_search_rsb_tree kernel: RDMA/umem: Fix double dma_buf_unpin in failure path kernel: tcp: fix potential race in tcp_v6_syn_recv_sock() kernel: netfilter: flowtable: strictly check for maximum number of actions kernel: scsi: qla2xxx: Completely fix fcport double free kernel: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows kernel: RDMA/rxe: Fix double free in rxe_srq_from_init kernel: ALSA: aloop: Fix peer runtime UAF during format-change stop kernel: exit: prevent preemption of oopsing TASK_DEAD task kernel: RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() kernel: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL kernel: netfilter: nft_inner: Fix IPv6 inner_thoff desync&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:34094</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21691</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21691</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cachestat: fix page cache statistics permission checking When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb (&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much more convenient (and performant) version of mincore() that didn&amp;#39;t need mapping things into the user virtual address space in order to work. But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore() more conservative&amp;#34;). This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file context (rather than vma).&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cachestat: fix page cache statistics permission checking When the &amp;#39;cachestat()&amp;#39; system call was added in commit cf264e1329fb (&amp;#34;cachestat: implement cachestat syscall&amp;#34;), it was meant to be a much more convenient (and performant) version of mincore() that didn&amp;#39;t need mapping things into the user virtual address space in order to work. But it ended up missing the &amp;#34;check for writability or ownership&amp;#34; fix for mincore(), done in commit 134fca9063ad (&amp;#34;mm/mincore.c: make mincore() more conservative&amp;#34;). This just adds equivalent logic to &amp;#39;cachestat()&amp;#39;, modified for the file context (rather than vma).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21691</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0309 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0309</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um seine Privilegien zu eskalieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um seine Privilegien zu eskalieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0309</guid>
    </item>
  </channel>
</rss>
