<?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 18:40:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-10772</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-10772</link>
      <description>bdu:2025-10772</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-10772</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38231</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38231</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-38231</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>EUVD-2026-336333</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-336333</link>
      <description>EUVD-2026-336333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-336333</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38231</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38231</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: Initialize ssc before laundromat_work to prevent NULL dereference&lt;/p&gt;
&lt;p&gt;In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through
nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized,
this can cause NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Normally the delayed start of laundromat_work allows sufficient time for
nfsd_ssc initialization to complete. However, when the kernel waits too
long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt;
nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt;
cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the
delayed work may start before nfsd_ssc initialization finishes.&lt;/p&gt;
&lt;p&gt;Fix this by moving nfsd_ssc initialization before starting laundromat_work.&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;nfsd: Initialize ssc before laundromat_work to prevent NULL dereference&lt;/p&gt;
&lt;p&gt;In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through
nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized,
this can cause NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Normally the delayed start of laundromat_work allows sufficient time for
nfsd_ssc initialization to complete. However, when the kernel waits too
long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt;
nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt;
cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the
delayed work may start before nfsd_ssc initialization finishes.&lt;/p&gt;
&lt;p&gt;Fix this by moving nfsd_ssc initialization before starting laundromat_work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38231</guid>
    </item>
    <item>
      <title>GHSA-7q5j-m65f-w95r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7q5j-m65f-w95r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: Initialize ssc before laundromat_work to prevent NULL dereference&lt;/p&gt;
&lt;p&gt;In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through
nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized,
this can cause NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Normally the delayed start of laundromat_work allows sufficient time for
nfsd_ssc initialization to complete. However, when the kernel waits too
long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt;
nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt;
cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the
delayed work may start before nfsd_ssc initialization finishes.&lt;/p&gt;
&lt;p&gt;Fix this by moving nfsd_ssc initialization before starting laundromat_work.&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;nfsd: Initialize ssc before laundromat_work to prevent NULL dereference&lt;/p&gt;
&lt;p&gt;In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through
nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized,
this can cause NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Normally the delayed start of laundromat_work allows sufficient time for
nfsd_ssc initialization to complete. However, when the kernel waits too
long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt;
nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt;
cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the
delayed work may start before nfsd_ssc initialization finishes.&lt;/p&gt;
&lt;p&gt;Fix this by moving nfsd_ssc initialization before starting laundromat_work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7q5j-m65f-w95r</guid>
    </item>
    <item>
      <title>ICSA-25-162-05 — Siemens SIMATIC S7-1500 CPU family</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-25-162-05</link>
      <description>&lt;p&gt;sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user. A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash. A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags. A buffer overflow was discovered in the GNU C Library&amp;#39;s dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment var…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user. A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash. A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags. A buffer overflow was discovered in the GNU C Library&amp;#39;s dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment var…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-25-162-05</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38231 — nfsd: Initialize ssc before laundromat_work to prevent NULL dereference</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38231</link>
      <description>msrc_CVE-2025-38231</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38231</guid>
    </item>
    <item>
      <title>OESA-2025-2776 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2776</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP2: 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;jfs: add check read-only before txBeginAnon() call&lt;/p&gt;
&lt;p&gt;Added a read-only check before calling `txBeginAnon` in `extAlloc`
and `extRecord`. This prevents modification attempts on a read-only
mounted filesystem, avoiding potential errors or crashes.&lt;/p&gt;
&lt;p&gt;Call trace:
 txBeginAnon+0xac/0x154
 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78
 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248
 __block_write_begin_int+0x580/0x166c fs/buffer.c:2128
 __block_write_begin fs/buffer.c:2177 [inline]
 block_write_begin+0x98/0x11c fs/buffer.c:2236
 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: zswap: properly synchronize freeing resources during CPU hotunplug&lt;/p&gt;
&lt;p&gt;In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the
current CPU at the beginning of the operation is retrieved and used
throughout.  However, since neither preemption nor migration are disabled,
it is possible that the operation continues on a different CPU.&lt;/p&gt;
&lt;p&gt;If the original CPU is hotunplugged while the acomp_ctx is still in use,
we run into a UAF bug as some of the resources attached to the acomp_ctx
are freed during hotunplug in zswap_cpu_comp_dead() (i.e. 
acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).&lt;/p&gt;
&lt;p&gt;The problem was introduced in commit 1ec3b5fe6eec (&amp;amp;quot;mm/zswap: move to use
crypto_acom…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP2: 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;jfs: add check read-only before txBeginAnon() call&lt;/p&gt;
&lt;p&gt;Added a read-only check before calling `txBeginAnon` in `extAlloc`
and `extRecord`. This prevents modification attempts on a read-only
mounted filesystem, avoiding potential errors or crashes.&lt;/p&gt;
&lt;p&gt;Call trace:
 txBeginAnon+0xac/0x154
 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78
 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248
 __block_write_begin_int+0x580/0x166c fs/buffer.c:2128
 __block_write_begin fs/buffer.c:2177 [inline]
 block_write_begin+0x98/0x11c fs/buffer.c:2236
 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: zswap: properly synchronize freeing resources during CPU hotunplug&lt;/p&gt;
&lt;p&gt;In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the
current CPU at the beginning of the operation is retrieved and used
throughout.  However, since neither preemption nor migration are disabled,
it is possible that the operation continues on a different CPU.&lt;/p&gt;
&lt;p&gt;If the original CPU is hotunplugged while the acomp_ctx is still in use,
we run into a UAF bug as some of the resources attached to the acomp_ctx
are freed during hotunplug in zswap_cpu_comp_dead() (i.e. 
acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).&lt;/p&gt;
&lt;p&gt;The problem was introduced in commit 1ec3b5fe6eec (&amp;amp;quot;mm/zswap: move to use
crypto_acom…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2776</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>SSA-082556 — SSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-082556</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.5 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;
&lt;p&gt;Note: This SSA advises vulnerabilities for firmware version V3.1.5 only; for version V3.1.6 refer to SSA-019113.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.5 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;
&lt;p&gt;Note: This SSA advises vulnerabilities for firmware version V3.1.5 only; for version V3.1.6 refer to SSA-019113.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-082556</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02853-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02853-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:02853-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38231</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38231</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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: Initialize ssc before laundromat_work to prevent NULL dereference In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized, this can cause NULL pointer dereference. Normally the delayed start of laundromat_work allows sufficient time for nfsd_ssc initialization to complete. However, when the kernel waits too long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt; nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt; cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the delayed work may start before nfsd_ssc initialization finishes. Fix this by moving nfsd_ssc initialization before starting laundromat_work.&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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: Initialize ssc before laundromat_work to prevent NULL dereference In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through nfs4_laundromat -&amp;gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn&amp;#39;t initialized, this can cause NULL pointer dereference. Normally the delayed start of laundromat_work allows sufficient time for nfsd_ssc initialization to complete. However, when the kernel waits too long for userspace responses (e.g. in nfs4_state_start_net -&amp;gt; nfsd4_end_grace -&amp;gt; nfsd4_record_grace_done -&amp;gt; nfsd4_cld_grace_done -&amp;gt; cld_pipe_upcall -&amp;gt; __cld_pipe_upcall -&amp;gt; wait_for_completion path), the delayed work may start before nfsd_ssc initialization finishes. Fix this by moving nfsd_ssc initialization before starting laundromat_work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38231</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1465 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1465</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-1465</guid>
    </item>
  </channel>
</rss>
