{"uuid": "b1900313-26b9-41bf-b071-387e4a2b6f9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42315", "type": "seen", "source": "https://t.me/cvedetector/3389", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42315 - \"Exfat Linux Kernel Deadlock in __exfat_get_dentry_set\"\", \n  \"Content\": \"CVE ID : CVE-2024-42315 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nexfat: fix potential deadlock on __exfat_get_dentry_set  \n  \nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array  \nis allocated in __exfat_get_entry_set. The problem is that the bh-array is  \nallocated with GFP_KERNEL. It does not make sense. In the following cases,  \na deadlock for sbi->s_lock between the two processes may occur.  \n  \n       CPU0                CPU1  \n       ----                ----  \n  kswapd  \n   balance_pgdat  \n    lock(fs_reclaim)  \n                      exfat_iterate  \n                       lock(&sbi->s_lock)  \n                       exfat_readdir  \n                        exfat_get_uniname_from_ext_entry  \n                         exfat_get_dentry_set  \n                          __exfat_get_dentry_set  \n                           kmalloc_array  \n                            ...  \n                            lock(fs_reclaim)  \n    ...  \n    evict  \n     exfat_evict_inode  \n      lock(&sbi->s_lock)  \n  \nTo fix this, let's allocate bh-array with GFP_NOFS. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:17:49.000000Z"}