<?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 06:11:23 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:16880 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:16880</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 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: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)
  * kernel: smb: client: fix use-after-free in cifs_oplock_break (CVE-2025-38527)
  * kernel: sctp: linearize cloned gso packets in sctp_rcv (CVE-2025-38718)
  * kernel: tls: fix handling of zero-length records on the rx_list (CVE-2025-39682)
  * kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure (CVE-2025-39698)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 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: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)
  * kernel: smb: client: fix use-after-free in cifs_oplock_break (CVE-2025-38527)
  * kernel: sctp: linearize cloned gso packets in sctp_rcv (CVE-2025-38718)
  * kernel: tls: fix handling of zero-length records on the rx_list (CVE-2025-39682)
  * kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure (CVE-2025-39698)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:16880</guid>
    </item>
    <item>
      <title>bdu:2025-12706</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12706</link>
      <description>bdu:2025-12706</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12706</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39698</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39698</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-39698</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — 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-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>EUVD-2026-347179</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347179</link>
      <description>EUVD-2026-347179</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347179</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39698</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39698</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;
&lt;p&gt;The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA
at that point. Those two should always go together, as the flag tells
io_uring whether the field is valid or not.&lt;/p&gt;
&lt;p&gt;Additionally, on failure cleanup, the futex handler frees the data but
does not clear -&amp;gt;async_data. Clear the data and the flag in the error
path as well.&lt;/p&gt;
&lt;p&gt;Thanks to Trend Micro Zero Day Initiative and particularly ReDress for
reporting this.&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;io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;
&lt;p&gt;The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA
at that point. Those two should always go together, as the flag tells
io_uring whether the field is valid or not.&lt;/p&gt;
&lt;p&gt;Additionally, on failure cleanup, the futex handler frees the data but
does not clear -&amp;gt;async_data. Clear the data and the flag in the error
path as well.&lt;/p&gt;
&lt;p&gt;Thanks to Trend Micro Zero Day Initiative and particularly ReDress for
reporting this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39698</guid>
    </item>
    <item>
      <title>GHSA-q7v5-hrgw-5gjh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q7v5-hrgw-5gjh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;
&lt;p&gt;The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA
at that point. Those two should always go together, as the flag tells
io_uring whether the field is valid or not.&lt;/p&gt;
&lt;p&gt;Additionally, on failure cleanup, the futex handler frees the data but
does not clear -&amp;gt;async_data. Clear the data and the flag in the error
path as well.&lt;/p&gt;
&lt;p&gt;Thanks to Trend Micro Zero Day Initiative and particularly ReDress for
reporting this.&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;io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;
&lt;p&gt;The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA
at that point. Those two should always go together, as the flag tells
io_uring whether the field is valid or not.&lt;/p&gt;
&lt;p&gt;Additionally, on failure cleanup, the futex handler frees the data but
does not clear -&amp;gt;async_data. Clear the data and the flag in the error
path as well.&lt;/p&gt;
&lt;p&gt;Thanks to Trend Micro Zero Day Initiative and particularly ReDress for
reporting this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q7v5-hrgw-5gjh</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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-2025:20081-1</guid>
    </item>
    <item>
      <title>RHSA-2025:16904 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:16904</link>
      <description>&lt;p&gt;kernel: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass kernel: cifs: Fix the smbd_response slab to allow usercopy kernel: smb: client: fix use-after-free in cifs_oplock_break kernel: tls: fix handling of zero-length records on the rx_list kernel: s390/sclp: Fix SCCB present check kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass kernel: cifs: Fix the smbd_response slab to allow usercopy kernel: smb: client: fix use-after-free in cifs_oplock_break kernel: tls: fix handling of zero-length records on the rx_list kernel: s390/sclp: Fix SCCB present check kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:16904</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21074-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21074-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:21074-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39698</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39698</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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on failure The io_futex_data is allocated upfront and assigned to the io_kiocb async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA at that point. Those two should always go together, as the flag tells io_uring whether the field is valid or not. Additionally, on failure cleanup, the futex handler frees the data but does not clear -&amp;gt;async_data. Clear the data and the flag in the error path as well. Thanks to Trend Micro Zero Day Initiative and particularly ReDress for reporting this.&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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on failure The io_futex_data is allocated upfront and assigned to the io_kiocb async_data field, but the request isn&amp;#39;t marked with REQ_F_ASYNC_DATA at that point. Those two should always go together, as the flag tells io_uring whether the field is valid or not. Additionally, on failure cleanup, the futex handler frees the data but does not clear -&amp;gt;async_data. Clear the data and the flag in the error path as well. Thanks to Trend Micro Zero Day Initiative and particularly ReDress for reporting this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39698</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1988 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</guid>
    </item>
  </channel>
</rss>
