https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 11:59:50 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53440 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nilfs2: fix sysfs interface lifetime</p> <p>The current nilfs2 sysfs support has issues with the timing of creation and deletion of sysfs entries, potentially leading to null pointer dereferences, use-after-free, and lockdep warnings.</p> <p>Some of the sysfs attributes for nilfs2 per-filesystem instance refer to metadata file &#34;cpfile&#34;, &#34;sufile&#34;, or &#34;dat&#34;, but nilfs_sysfs_create_device_group that creates those attributes is executed before the inodes for these metadata files are loaded, and nilfs_sysfs_delete_device_group which deletes these sysfs entries is called after releasing their metadata file inodes.</p> <p>Therefore, access to some of these sysfs attributes may occur outside of the lifetime of these metadata files, resulting in inode NULL pointer dereferences or use-after-free.</p> <p>In addition, the call to nilfs_sysfs_create_device_group() is made during the locking period of the semaphore &#34;ns_sem&#34; of nilfs object, so the shrinker call caused by the memory allocation for the sysfs entries, may derive lock dependencies &#34;ns_sem&#34; -&gt; (shrinker) -&gt; &#34;locks acquired in nilfs_evict_inode()&#34;.</p> <p>Since nilfs2 may acquire &#34;ns_sem&#34; deep in the call stack holding other locks via its error handler __nilfs_error(), this causes lockdep to report circular locking. This is a false positive and no circular locking actually occurs as no inodes exist yet when nilfs_sysfs_create_device_group() is called. Fortunately, the lockdep warnings ca…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nilfs2: fix sysfs interface lifetime</p> <p>The current nilfs2 sysfs support has issues with the timing of creation and deletion of sysfs entries, potentially leading to null pointer dereferences, use-after-free, and lockdep warnings.</p> <p>Some of the sysfs attributes for nilfs2 per-filesystem instance refer to metadata file &#34;cpfile&#34;, &#34;sufile&#34;, or &#34;dat&#34;, but nilfs_sysfs_create_device_group that creates those attributes is executed before the inodes for these metadata files are loaded, and nilfs_sysfs_delete_device_group which deletes these sysfs entries is called after releasing their metadata file inodes.</p> <p>Therefore, access to some of these sysfs attributes may occur outside of the lifetime of these metadata files, resulting in inode NULL pointer dereferences or use-after-free.</p> <p>In addition, the call to nilfs_sysfs_create_device_group() is made during the locking period of the semaphore &#34;ns_sem&#34; of nilfs object, so the shrinker call caused by the memory allocation for the sysfs entries, may derive lock dependencies &#34;ns_sem&#34; -&gt; (shrinker) -&gt; &#34;locks acquired in nilfs_evict_inode()&#34;.</p> <p>Since nilfs2 may acquire &#34;ns_sem&#34; deep in the call stack holding other locks via its error handler __nilfs_error(), this causes lockdep to report circular locking. This is a false positive and no circular locking actually occurs as no inodes exist yet when nilfs_sysfs_create_device_group() is called. Fortunately, the lockdep warnings ca…</p> https://vulnerability.circl.lu/vuln/cve-2023-53440