<?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 12:43:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06108</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06108</link>
      <description>bdu:2025-06108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06108</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21639</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-21639</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-21639</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0134 — 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-0134</link>
      <description>certfr-2025-avi-0134</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0134</guid>
    </item>
    <item>
      <title>EUVD-2026-317107</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-317107</link>
      <description>EUVD-2026-317107</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-317107</guid>
    </item>
    <item>
      <title>fkie_cve-2025-21639</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21639</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy&lt;/p&gt;
&lt;p&gt;As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39;
structure via &amp;#39;current&amp;#39; is not recommended for different reasons:&lt;/p&gt;
&lt;p&gt;- Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only
  from the opener&amp;#39;s netns.&lt;/p&gt;
&lt;p&gt;- current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;
  (null-ptr-deref), e.g. when the current task is exiting, as spotted by
  syzbot [1] using acct(2).&lt;/p&gt;
&lt;p&gt;The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using
container_of().&lt;/p&gt;
&lt;p&gt;Note that table-&amp;gt;data could also be used directly, as this is the only
member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size
of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&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;sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy&lt;/p&gt;
&lt;p&gt;As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39;
structure via &amp;#39;current&amp;#39; is not recommended for different reasons:&lt;/p&gt;
&lt;p&gt;- Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only
  from the opener&amp;#39;s netns.&lt;/p&gt;
&lt;p&gt;- current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;
  (null-ptr-deref), e.g. when the current task is exiting, as spotted by
  syzbot [1] using acct(2).&lt;/p&gt;
&lt;p&gt;The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using
container_of().&lt;/p&gt;
&lt;p&gt;Note that table-&amp;gt;data could also be used directly, as this is the only
member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size
of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-21639</guid>
    </item>
    <item>
      <title>GHSA-6w8c-3g24-p9jh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6w8c-3g24-p9jh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy&lt;/p&gt;
&lt;p&gt;As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39;
structure via &amp;#39;current&amp;#39; is not recommended for different reasons:&lt;/p&gt;
&lt;p&gt;- Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only
  from the opener&amp;#39;s netns.&lt;/p&gt;
&lt;p&gt;- current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;
  (null-ptr-deref), e.g. when the current task is exiting, as spotted by
  syzbot [1] using acct(2).&lt;/p&gt;
&lt;p&gt;The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using
container_of().&lt;/p&gt;
&lt;p&gt;Note that table-&amp;gt;data could also be used directly, as this is the only
member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size
of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&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;sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy&lt;/p&gt;
&lt;p&gt;As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39;
structure via &amp;#39;current&amp;#39; is not recommended for different reasons:&lt;/p&gt;
&lt;p&gt;- Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only
  from the opener&amp;#39;s netns.&lt;/p&gt;
&lt;p&gt;- current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;
  (null-ptr-deref), e.g. when the current task is exiting, as spotted by
  syzbot [1] using acct(2).&lt;/p&gt;
&lt;p&gt;The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using
container_of().&lt;/p&gt;
&lt;p&gt;Note that table-&amp;gt;data could also be used directly, as this is the only
member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size
of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6w8c-3g24-p9jh</guid>
    </item>
    <item>
      <title>ICSA-24-102-01 — Siemens SIMATIC S7-1500 TM MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-24-102-01</link>
      <description>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-24-102-01</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-21639 — sctp: sysctl: rto_min/max: avoid using current-&gt;nsproxy</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-21639</link>
      <description>msrc_CVE-2025-21639</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-21639</guid>
    </item>
    <item>
      <title>OESA-2025-1320 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1320</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.&lt;/p&gt;
&lt;p&gt;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;RDMA/rtrs: Ensure &amp;amp;apos;ib_sge list&amp;amp;apos; is accessible&lt;/p&gt;
&lt;p&gt;Move the declaration of the &amp;amp;apos;ib_sge list&amp;amp;apos; variable outside the
&amp;amp;apos;always_invalidate&amp;amp;apos; block to ensure it remains accessible for use
throughout the function.&lt;/p&gt;
&lt;p&gt;Previously, &amp;amp;apos;ib_sge list&amp;amp;apos; was declared within the &amp;amp;apos;always_invalidate&amp;amp;apos;
block, limiting its accessibility, then caused a
&amp;amp;apos;BUG: kernel NULL pointer dereference&amp;amp;apos;[1].
 ? __die_body.cold+0x19/0x27
 ? page_fault_oops+0x15a/0x2d0
 ? search_module_extables+0x19/0x60
 ? search_bpf_extables+0x5f/0x80
 ? exc_page_fault+0x7e/0x180
 ? asm_exc_page_fault+0x26/0x30
 ? memcpy_orig+0xd5/0x140
 rxe_mr_copy+0x1c3/0x200 [rdma_rxe]
 ? rxe_pool_get_index+0x4b/0x80 [rdma_rxe]
 copy_data+0xa5/0x230 [rdma_rxe]
 rxe_requester+0xd9b/0xf70 [rdma_rxe]
 ? finish_task_switch.isra.0+0x99/0x2e0
 rxe_sender+0x13/0x40 [rdma_rxe]
 do_task+0x68/0x1e0 [rdma_rxe]
 process_one_work+0x177/0x330
 worker_thread+0x252/0x390
 ? __pfx_worker_thread+0x10/0x10&lt;/p&gt;
&lt;p&gt;This change ensures the variable is available for subsequent operations
that require it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-rdma/6a1f3e8f-deb0-49f9-bc69-a9b03ecfcda7@fujitsu.com/(CVE-2024-36476)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check&lt;/p&gt;
&lt;p&gt;The return value of drm_at…&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.&lt;/p&gt;
&lt;p&gt;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;RDMA/rtrs: Ensure &amp;amp;apos;ib_sge list&amp;amp;apos; is accessible&lt;/p&gt;
&lt;p&gt;Move the declaration of the &amp;amp;apos;ib_sge list&amp;amp;apos; variable outside the
&amp;amp;apos;always_invalidate&amp;amp;apos; block to ensure it remains accessible for use
throughout the function.&lt;/p&gt;
&lt;p&gt;Previously, &amp;amp;apos;ib_sge list&amp;amp;apos; was declared within the &amp;amp;apos;always_invalidate&amp;amp;apos;
block, limiting its accessibility, then caused a
&amp;amp;apos;BUG: kernel NULL pointer dereference&amp;amp;apos;[1].
 ? __die_body.cold+0x19/0x27
 ? page_fault_oops+0x15a/0x2d0
 ? search_module_extables+0x19/0x60
 ? search_bpf_extables+0x5f/0x80
 ? exc_page_fault+0x7e/0x180
 ? asm_exc_page_fault+0x26/0x30
 ? memcpy_orig+0xd5/0x140
 rxe_mr_copy+0x1c3/0x200 [rdma_rxe]
 ? rxe_pool_get_index+0x4b/0x80 [rdma_rxe]
 copy_data+0xa5/0x230 [rdma_rxe]
 rxe_requester+0xd9b/0xf70 [rdma_rxe]
 ? finish_task_switch.isra.0+0x99/0x2e0
 rxe_sender+0x13/0x40 [rdma_rxe]
 do_task+0x68/0x1e0 [rdma_rxe]
 process_one_work+0x177/0x330
 worker_thread+0x252/0x390
 ? __pfx_worker_thread+0x10/0x10&lt;/p&gt;
&lt;p&gt;This change ensures the variable is available for subsequent operations
that require it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-rdma/6a1f3e8f-deb0-49f9-bc69-a9b03ecfcda7@fujitsu.com/(CVE-2024-36476)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check&lt;/p&gt;
&lt;p&gt;The return value of drm_at…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1320</guid>
    </item>
    <item>
      <title>SSA-265688 — SSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-265688</link>
      <description>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-265688</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0784-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0784-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:0784-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21639</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21639</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39; structure via &amp;#39;current&amp;#39; is not recommended for different reasons: - Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only   from the opener&amp;#39;s netns. - current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;   (null-ptr-deref), e.g. when the current task is exiting, as spotted by   syzbot [1] using acct(2). The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using container_of(). Note that table-&amp;gt;data could also be used directly, as this is the only member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current-&amp;gt;nsproxy As mentioned in a previous commit of this series, using the &amp;#39;net&amp;#39; structure via &amp;#39;current&amp;#39; is not recommended for different reasons: - Inconsistency: getting info from the reader&amp;#39;s/writer&amp;#39;s netns vs only   from the opener&amp;#39;s netns. - current-&amp;gt;nsproxy can be NULL in some cases, resulting in an &amp;#39;Oops&amp;#39;   (null-ptr-deref), e.g. when the current task is exiting, as spotted by   syzbot [1] using acct(2). The &amp;#39;net&amp;#39; structure can be obtained from the table-&amp;gt;data using container_of(). Note that table-&amp;gt;data could also be used directly, as this is the only member needed from the &amp;#39;net&amp;#39; structure, but that would increase the size of this fix, to use &amp;#39;*data&amp;#39; everywhere &amp;#39;net-&amp;gt;sctp.rto_min/max&amp;#39; is used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21639</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0119</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0119</guid>
    </item>
  </channel>
</rss>
