https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 07:30:23 +0000 https://cve.radiocsirt.org/vuln/cve-2024-42315 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>exfat: fix potential deadlock on __exfat_get_dentry_set</p> <p>When accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array is allocated in __exfat_get_entry_set. The problem is that the bh-array is allocated with GFP_KERNEL. It does not make sense. In the following cases, a deadlock for sbi-&gt;s_lock between the two processes may occur.</p> <p>CPU0 CPU1 ---- ---- kswapd balance_pgdat lock(fs_reclaim) exfat_iterate lock(&amp;sbi-&gt;s_lock) exfat_readdir exfat_get_uniname_from_ext_entry exfat_get_dentry_set __exfat_get_dentry_set kmalloc_array ... lock(fs_reclaim) ... evict exfat_evict_inode lock(&amp;sbi-&gt;s_lock)</p> <p>To fix this, let&#39;s allocate bh-array with GFP_NOFS.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>exfat: fix potential deadlock on __exfat_get_dentry_set</p> <p>When accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array is allocated in __exfat_get_entry_set. The problem is that the bh-array is allocated with GFP_KERNEL. It does not make sense. In the following cases, a deadlock for sbi-&gt;s_lock between the two processes may occur.</p> <p>CPU0 CPU1 ---- ---- kswapd balance_pgdat lock(fs_reclaim) exfat_iterate lock(&amp;sbi-&gt;s_lock) exfat_readdir exfat_get_uniname_from_ext_entry exfat_get_dentry_set __exfat_get_dentry_set kmalloc_array ... lock(fs_reclaim) ... evict exfat_evict_inode lock(&amp;sbi-&gt;s_lock)</p> <p>To fix this, let&#39;s allocate bh-array with GFP_NOFS.</p> https://cve.radiocsirt.org/vuln/cve-2024-42315