CVE-2024-57940Medium

Microsoft security update for CVE-2024-57940

Published
March 13, 2025
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-57940. This page also shows what EchelonGraph holds for CVE-2024-57940, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • azl3 kernel 6.6.64.2-9 on Azure Linux 3.0
  • azl3 kernel 6.6.76.1-1 on Azure Linux 3.0
  • cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 3 updates

3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update5.15.179.1-1
—Security Update6.6.76.1-1
—Security Update—

🧭 EchelonGraph on CVE-2024-57940

EchelonGraph score
5.5 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

In the Linux kernel, the following vulnerability has been resolved: exfat: fix the infinite loop in exfat_readdir() If the file system is corrupted so that a cluster is linked to itself in the cluster chain, and there is an unused directory entry in the cluster, 'dentry' will not be incremented, causing condition 'dentry < max_dentries' unable to prevent an infinite loop. This infinite loop causes s_lock not to be released, and other tasks will hang, such as exfat_sync_fs(). This commit stops traversing the cluster chain when there is unused directory entry in the cluster to avoid this infinite loop.

Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-57940, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)