<?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>Wed, 14 Oct 2026 21:12:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53690 — nilfs2: prevent use of deleted inode</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-53690</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: prevent use of deleted inode&lt;/p&gt;
&lt;p&gt;syzbot reported a WARNING in nilfs_rmdir. [1]&lt;/p&gt;
&lt;p&gt;Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a &amp;#34;.nilfs&amp;#34; file was reassigned by nilfs_mkdir for &amp;#34;file0&amp;#34;,
causing an inode duplication during execution.  And this causes an
underflow of i_nlink in rmdir operations.&lt;/p&gt;
&lt;p&gt;The inode is used twice by the same task to unmount and remove directories
&amp;#34;.nilfs&amp;#34; and &amp;#34;file0&amp;#34;, it trigger warning in nilfs_rmdir.&lt;/p&gt;
&lt;p&gt;Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
 do_rmdir+0x3b5/0x580 fs/namei.c:4453
 __do_sys_rmdir fs/namei.c:4472 [inline]
 __se_sys_rmdir fs/namei.c:4470 [inline]
 __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: prevent use of deleted inode&lt;/p&gt;
&lt;p&gt;syzbot reported a WARNING in nilfs_rmdir. [1]&lt;/p&gt;
&lt;p&gt;Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a &amp;#34;.nilfs&amp;#34; file was reassigned by nilfs_mkdir for &amp;#34;file0&amp;#34;,
causing an inode duplication during execution.  And this causes an
underflow of i_nlink in rmdir operations.&lt;/p&gt;
&lt;p&gt;The inode is used twice by the same task to unmount and remove directories
&amp;#34;.nilfs&amp;#34; and &amp;#34;file0&amp;#34;, it trigger warning in nilfs_rmdir.&lt;/p&gt;
&lt;p&gt;Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
 do_rmdir+0x3b5/0x580 fs/namei.c:4453
 __do_sys_rmdir fs/namei.c:4472 [inline]
 __se_sys_rmdir fs/namei.c:4470 [inline]
 __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-53690</guid>
    </item>
    <item>
      <title>USN-7379-1 — linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7379-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7379-1</guid>
    </item>
  </channel>
</rss>
