<?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>Mon, 19 Oct 2026 09:53:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04533</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04533</link>
      <description>bdu:2026-04533</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04533</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53167</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53167</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-53167</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — 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-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-346426</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346426</link>
      <description>EUVD-2026-346426</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346426</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53167</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53167</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device&lt;/p&gt;
&lt;p&gt;Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key
unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may
dereference a NULL block_device in:&lt;/p&gt;
&lt;p&gt;bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]
  bl_free_device+0x70/0x80 [blocklayoutdriver]
  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]
  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]
  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]
  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]
  nfs4_destroy_server+0x36/0x70 [nfsv4]
  nfs_free_server+0x23/0xe0 [nfs]
  deactivate_locked_super+0x30/0xb0
  cleanup_mnt+0xba/0x150
  task_work_run+0x59/0x90
  syscall_exit_to_user_mode+0x217/0x220
  do_syscall_64+0x8e/0x160&lt;/p&gt;
&lt;p&gt;This happens because even though we were able to create the
nfs4_deviceid_node, the lookup for the device was unable to attach the
block device to the pnfs_block_dev.&lt;/p&gt;
&lt;p&gt;If we never found a block device to register, we can avoid this case with
the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the
flag.&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;nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device&lt;/p&gt;
&lt;p&gt;Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key
unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may
dereference a NULL block_device in:&lt;/p&gt;
&lt;p&gt;bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]
  bl_free_device+0x70/0x80 [blocklayoutdriver]
  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]
  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]
  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]
  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]
  nfs4_destroy_server+0x36/0x70 [nfsv4]
  nfs_free_server+0x23/0xe0 [nfs]
  deactivate_locked_super+0x30/0xb0
  cleanup_mnt+0xba/0x150
  task_work_run+0x59/0x90
  syscall_exit_to_user_mode+0x217/0x220
  do_syscall_64+0x8e/0x160&lt;/p&gt;
&lt;p&gt;This happens because even though we were able to create the
nfs4_deviceid_node, the lookup for the device was unable to attach the
block device to the pnfs_block_dev.&lt;/p&gt;
&lt;p&gt;If we never found a block device to register, we can avoid this case with
the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the
flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53167</guid>
    </item>
    <item>
      <title>GHSA-2f9p-c2rc-cff7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2f9p-c2rc-cff7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device&lt;/p&gt;
&lt;p&gt;Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key
unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may
dereference a NULL block_device in:&lt;/p&gt;
&lt;p&gt;bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]
  bl_free_device+0x70/0x80 [blocklayoutdriver]
  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]
  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]
  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]
  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]
  nfs4_destroy_server+0x36/0x70 [nfsv4]
  nfs_free_server+0x23/0xe0 [nfs]
  deactivate_locked_super+0x30/0xb0
  cleanup_mnt+0xba/0x150
  task_work_run+0x59/0x90
  syscall_exit_to_user_mode+0x217/0x220
  do_syscall_64+0x8e/0x160&lt;/p&gt;
&lt;p&gt;This happens because even though we were able to create the
nfs4_deviceid_node, the lookup for the device was unable to attach the
block device to the pnfs_block_dev.&lt;/p&gt;
&lt;p&gt;If we never found a block device to register, we can avoid this case with
the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the
flag.&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;nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device&lt;/p&gt;
&lt;p&gt;Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key
unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may
dereference a NULL block_device in:&lt;/p&gt;
&lt;p&gt;bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]
  bl_free_device+0x70/0x80 [blocklayoutdriver]
  bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]
  nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]
  nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]
  unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]
  nfs4_destroy_server+0x36/0x70 [nfsv4]
  nfs_free_server+0x23/0xe0 [nfs]
  deactivate_locked_super+0x30/0xb0
  cleanup_mnt+0xba/0x150
  task_work_run+0x59/0x90
  syscall_exit_to_user_mode+0x217/0x220
  do_syscall_64+0x8e/0x160&lt;/p&gt;
&lt;p&gt;This happens because even though we were able to create the
nfs4_deviceid_node, the lookup for the device was unable to attach the
block device to the pnfs_block_dev.&lt;/p&gt;
&lt;p&gt;If we never found a block device to register, we can avoid this case with
the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the
flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2f9p-c2rc-cff7</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53167</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53167</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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may dereference a NULL block_device in:   bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]   bl_free_device+0x70/0x80 [blocklayoutdriver]   bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]   nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]   nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]   unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]   nfs4_destroy_server+0x36/0x70 [nfsv4]   nfs_free_server+0x23/0xe0 [nfs]   deactivate_locked_super+0x30/0xb0   cleanup_mnt+0xba/0x150   task_work_run+0x59/0x90   syscall_exit_to_user_mode+0x217/0x220   do_syscall_64+0x8e/0x160 This happens because even though we were able to create the nfs4_deviceid_node, the lookup for the device was unable to attach the block device to the pnfs_block_dev. If we never found a block device to register, we can avoid this case with the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the flag.&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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfs/blocklayout: Don&amp;#39;t attempt unregister for invalid block device Since commit d869da91cccb (&amp;#34;nfs/blocklayout: Fix premature PR key unregistration&amp;#34;) an unmount of a pNFS SCSI layout-enabled NFS may dereference a NULL block_device in:   bl_unregister_scsi+0x16/0xe0 [blocklayoutdriver]   bl_free_device+0x70/0x80 [blocklayoutdriver]   bl_free_deviceid_node+0x12/0x30 [blocklayoutdriver]   nfs4_put_deviceid_node+0x60/0xc0 [nfsv4]   nfs4_deviceid_purge_client+0x132/0x190 [nfsv4]   unset_pnfs_layoutdriver+0x59/0x60 [nfsv4]   nfs4_destroy_server+0x36/0x70 [nfsv4]   nfs_free_server+0x23/0xe0 [nfs]   deactivate_locked_super+0x30/0xb0   cleanup_mnt+0xba/0x150   task_work_run+0x59/0x90   syscall_exit_to_user_mode+0x217/0x220   do_syscall_64+0x8e/0x160 This happens because even though we were able to create the nfs4_deviceid_node, the lookup for the device was unable to attach the block device to the pnfs_block_dev. If we never found a block device to register, we can avoid this case with the PNFS_BDEV_REGISTERED flag.  Move the deref behind the test for the flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53167</guid>
    </item>
  </channel>
</rss>
