LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42315: exfat: fix potential deadlock on __exfat_get_dentry_set

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42315 is a Linux kernel exFAT filesystem deadlock flaw. Under specific memory pressure and exFAT directory-access conditions, the kernel can hang while waiting on filesystem locks. The sources do not provide CVSS, CWE, or active-exploitation evidence.

Executive priority

Treat as a targeted stability risk, not an emergency exploitation item based on current evidence. Prioritize patching where exFAT media is common, such as endpoints, kiosks, forensic workstations, and file-transfer systems.

Technical view

In __exfat_get_dentry_set, bh-array allocation used GFP_KERNEL while sbi->s_lock could be held. Memory reclaim may re-enter exFAT inode eviction and wait on the same lock, causing deadlock. The kernel fix changes this allocation to GFP_NOFS.

Likely exposure

Exposure is most relevant to Linux systems that mount exFAT filesystems, including removable media or disk images. The bundle lists affected Linux kernel versions and stable commits, but does not provide CPEs or distribution-wide coverage beyond Debian LTS notices.

Exploitation context

The CVE source describes a potential deadlock, not code execution or privilege escalation. KEV is false, and the provided sources do not state active exploitation or public weaponization.

Researcher notes

Evidence supports a kernel deadlock caused by GFP_KERNEL allocation under exFAT locking during memory reclaim. The bundle lacks CVSS, CWE, exploitability detail, and precise downstream package mapping except Debian LTS references.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable exFAT fixes.
  • Review Debian LTS announcements if running Debian LTS kernel packages.
  • Restrict mounting untrusted exFAT media until patched where operationally feasible.
  • Check vendor guidance for exact fixed package versions and reboot requirements.

Validation and detection

  • Inventory Linux hosts that mount exFAT filesystems or accept removable media.
  • Confirm running kernels include the referenced stable commits or vendor fixed packages.
  • Check Debian LTS systems against the cited DLA kernel update notices.
  • Review incident records for unexplained hangs during exFAT directory access.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42315 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbd3bdb9e0d656f760b11d0c638d35d7f7068144d, 92dcd7d6c6068bf4fd35a6f64d606e27d634807e, d8fe01ad2d8ab33aaf8f2efad9e8f1dae11c4b0c, a3ff29a95fde16906304455aa8c0bd84eb770258, a3ff29a95fde16906304455aa8c0bd84eb770258, a3ff29a95fde16906304455aa8c0bd84eb770258, 5.10.190, 5.15.150unaffected
LinuxLinux6.2, 0, 5.10.232, 5.15.175, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.