Vulnerability in Linux
CVE-2024-42315
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.002, 6.1th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Linux — versions 92dcd7d6c6068bf4fd35a6f64d606e27d634807e, bd3bdb9e0d656f760b11d0c638d35d7f7068144d, 5.10.190
- Linux Kernel
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (w4zu/Debian_security). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- git.kernel.org/stable/c/632fb232b6bbf8277edcbe9ecd4b4d98ecb122eb
- git.kernel.org/stable/c/c052f775ee6ccacd3c97e4cf41a2a657e63d4259
- git.kernel.org/stable/c/cd1c7858641384191ff7033fb1fc65dfcd559c6f
- git.kernel.org/stable/c/a7ac198f8dba791e3144c4da48a5a9b95773ee4b (Patch)
- git.kernel.org/stable/c/1d1970493c289e3f44b9ec847ed26a5dbdf56a62 (Patch)
- git.kernel.org/stable/c/89fc548767a2155231128cb98726d6d2ea1256c9 (Patch)
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html