exfat: fix potential deadlock on __exfat_get_dentry_set
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a3ff29a95fde16906304455aa8c0bd84eb770258 · < 89fc548767a2155231128cb98726d6d2ea1256c9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
exfat: fix potential deadlock on __exfat_get_dentry_set
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->s_lock between the two processes may occur.
CPU0 CPU1 ---- ---- kswapd balance_pgdat lock(fs_reclaim) exfat_iterate lock(&sbi->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(&sbi->s_lock)
To fix this, let's allocate bh-array with GFP_NOFS.
From the CVE record · Linux
The Linux kernel’s exfat code can deadlock when a file with more entries than ES_MAX_ENTRY_NUM is accessed during filesystem reclaim. An attacker who can cause that access may trigger the deadlock; the input does not specify network access, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with exfat support should check their kernel versions against the vendor advisory; affected versions were not provided.