CVE-2024-42315: exfat: fix potential deadlock on __exfat_get_dentry_set
First published: Sat Aug 17 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.2<6.6.44 | |
| Linux Kernel | >=6.7<6.10.3 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.133-1 6.12.22-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/1d1970493c289e3f44b9ec847ed26a5dbdf56a62
- https://git.kernel.org/stable/c/89fc548767a2155231128cb98726d6d2ea1256c9
- https://git.kernel.org/stable/c/a7ac198f8dba791e3144c4da48a5a9b95773ee4b
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42315
- https://nvd.nist.gov/vuln/detail/CVE-2024-42315
- https://launchpad.net/bugs/cve/CVE-2024-42315
- https://security-tracker.debian.org/tracker/CVE-2024-42315
- https://ubuntu.com/security/CVE-2024-42315
- https://git.kernel.org/linus/89fc548767a2155231128cb98726d6d2ea1256c9
- https://git.kernel.org/stable/c/632fb232b6bbf8277edcbe9ecd4b4d98ecb122eb
- https://git.kernel.org/stable/c/c052f775ee6ccacd3c97e4cf41a2a657e63d4259
- https://git.kernel.org/stable/c/cd1c7858641384191ff7033fb1fc65dfcd559c6f
Frequently Asked Questions
What is the severity of CVE-2024-42315?
CVE-2024-42315 is classified as a moderate severity vulnerability due to the potential for deadlocks in the Linux kernel.
How do I fix CVE-2024-42315?
To fix CVE-2024-42315, upgrade to a patched version of the Linux kernel, such as 6.1.123-1, 6.12.10-1, or 6.12.11-1.
What systems are affected by CVE-2024-42315?
CVE-2024-42315 affects specific versions of the Linux kernel, including versions between 6.2 and 6.6.44 and 6.7 to 6.10.3.
What is the impact of CVE-2024-42315?
The impact of CVE-2024-42315 includes potential deadlock situations when accessing files with excessive entries.
Is there a workaround for CVE-2024-42315?
There are no documented workarounds for CVE-2024-42315; updating the kernel is recommended for a fix.
- agent/title
- agent/first-publish-date
- agent/type
- agent/remedy
- agent/severity
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/references
- agent/trending
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- agent/softwarecombine
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/tags
- agent/event
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- agent/description
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.2
- version/linux kernel/6.7
- package-manager/debian