<?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, 09 Oct 2026 12:57:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03758</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03758</link>
      <description>bdu:2025-03758</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03758</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-46682</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-46682</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-2024-46682</guid>
    </item>
    <item>
      <title>cnvd-2024-39357</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-39357</link>
      <description>cnvd-2024-39357</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-39357</guid>
    </item>
    <item>
      <title>EUVD-2026-313223</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313223</link>
      <description>EUVD-2026-313223</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313223</guid>
    </item>
    <item>
      <title>fkie_cve-2024-46682</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-46682</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open&lt;/p&gt;
&lt;p&gt;Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of
sc_type&amp;#34;) states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.&lt;/p&gt;
&lt;p&gt;Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.&lt;/p&gt;
&lt;p&gt;To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc/fs/nfsd/clients/2/states&lt;/p&gt;
&lt;p&gt;[  513.590804] Call trace:
[  513.590925]  _raw_spin_lock+0xcc/0x160
[  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd]
[  513.591412]  states_show+0x44c/0x488 [nfsd]
[  513.591681]  seq_read_iter+0x5d8/0x760
[  513.591896]  seq_read+0x188/0x208
[  513.592075]  vfs_read+0x148/0x470
[  513.592241]  ksys_read+0xcc/0x178&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: prevent panic for nfsv4.0 closed files in nfs4_show_open&lt;/p&gt;
&lt;p&gt;Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of
sc_type&amp;#34;) states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.&lt;/p&gt;
&lt;p&gt;Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.&lt;/p&gt;
&lt;p&gt;To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc/fs/nfsd/clients/2/states&lt;/p&gt;
&lt;p&gt;[  513.590804] Call trace:
[  513.590925]  _raw_spin_lock+0xcc/0x160
[  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd]
[  513.591412]  states_show+0x44c/0x488 [nfsd]
[  513.591681]  seq_read_iter+0x5d8/0x760
[  513.591896]  seq_read+0x188/0x208
[  513.592075]  vfs_read+0x148/0x470
[  513.592241]  ksys_read+0xcc/0x178&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-46682</guid>
    </item>
    <item>
      <title>GHSA-xrjv-8x73-5h7v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xrjv-8x73-5h7v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open&lt;/p&gt;
&lt;p&gt;Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of
sc_type&amp;#34;) states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.&lt;/p&gt;
&lt;p&gt;Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.&lt;/p&gt;
&lt;p&gt;To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc/fs/nfsd/clients/2/states&lt;/p&gt;
&lt;p&gt;[  513.590804] Call trace:
[  513.590925]  _raw_spin_lock+0xcc/0x160
[  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd]
[  513.591412]  states_show+0x44c/0x488 [nfsd]
[  513.591681]  seq_read_iter+0x5d8/0x760
[  513.591896]  seq_read+0x188/0x208
[  513.592075]  vfs_read+0x148/0x470
[  513.592241]  ksys_read+0xcc/0x178&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: prevent panic for nfsv4.0 closed files in nfs4_show_open&lt;/p&gt;
&lt;p&gt;Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of
sc_type&amp;#34;) states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.&lt;/p&gt;
&lt;p&gt;Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.&lt;/p&gt;
&lt;p&gt;To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc/fs/nfsd/clients/2/states&lt;/p&gt;
&lt;p&gt;[  513.590804] Call trace:
[  513.590925]  _raw_spin_lock+0xcc/0x160
[  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd]
[  513.591412]  states_show+0x44c/0x488 [nfsd]
[  513.591681]  seq_read_iter+0x5d8/0x760
[  513.591896]  seq_read+0x188/0x208
[  513.592075]  vfs_read+0x148/0x470
[  513.592241]  ksys_read+0xcc/0x178&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xrjv-8x73-5h7v</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46682</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46682</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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of sc_type&amp;#34;) states_show() relied on sc_type field to be of valid type before calling into a subfunction to show content of a particular stateid. From that commit, we split the validity of the stateid into sc_status and no longer changed sc_type to 0 while unhashing the stateid. This resulted in kernel oopsing for nfsv4.0 opens that stay around and in nfs4_show_open() would derefence sc_file which was NULL. Instead, for closed open stateids forgo displaying information that relies of having a valid sc_file. To reproduce: mount the server with 4.0, read and close a file and then on the server cat /proc/fs/nfsd/clients/2/states [  513.590804] Call trace: [  513.590925]  _raw_spin_lock+0xcc/0x160 [  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd] [  513.591412]  states_show+0x44c/0x488 [nfsd] [  513.591681]  seq_read_iter+0x5d8/0x760 [  513.591896]  seq_read+0x188/0x208 [  513.592075]  vfs_read+0x148/0x470 [  513.592241]  ksys_read+0xcc/0x178&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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open Prior to commit 3f29cc82a84c (&amp;#34;nfsd: split sc_status out of sc_type&amp;#34;) states_show() relied on sc_type field to be of valid type before calling into a subfunction to show content of a particular stateid. From that commit, we split the validity of the stateid into sc_status and no longer changed sc_type to 0 while unhashing the stateid. This resulted in kernel oopsing for nfsv4.0 opens that stay around and in nfs4_show_open() would derefence sc_file which was NULL. Instead, for closed open stateids forgo displaying information that relies of having a valid sc_file. To reproduce: mount the server with 4.0, read and close a file and then on the server cat /proc/fs/nfsd/clients/2/states [  513.590804] Call trace: [  513.590925]  _raw_spin_lock+0xcc/0x160 [  513.591119]  nfs4_show_open+0x78/0x2c0 [nfsd] [  513.591412]  states_show+0x44c/0x488 [nfsd] [  513.591681]  seq_read_iter+0x5d8/0x760 [  513.591896]  seq_read+0x188/0x208 [  513.592075]  vfs_read+0x148/0x470 [  513.592241]  ksys_read+0xcc/0x178&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46682</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2133 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2133</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&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 einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2133</guid>
    </item>
  </channel>
</rss>
