CVE-2024-50065: ntfs3: Change to non-blocking allocation in ntfs_d_hash

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: Change to non-blocking allocation in ntfsdhash

dhash is done while under "rcu-walk" and should not sleep. getname() allocates using GFPKERNEL, having the possibility to sleep when under memory pressure. Change the allocation to GFPNOWAIT.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

5 affected componentsFixes available
Linux Linux kernel>=6.6.44<6.6.57
Linux Linux kernel>=6.11<6.11.4
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

Event History

Oct 21, 2024
CVE Published
via MITRE·07:39 PM
Data Sourced
via MITRE·07:39 PM
Description
Feb 20, 2025
Data Sourced
via Launchpad·12:47 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·01:06 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-50065?

CVE-2024-50065 has a high severity rating due to the potential for denial of service caused by non-blocking allocation issues in the Linux kernel.

2

How do I fix CVE-2024-50065?

To fix CVE-2024-50065, update your Linux kernel to a version that is not affected, such as 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.15-1.

3

Which Linux kernel versions are affected by CVE-2024-50065?

CVE-2024-50065 affects Linux kernel versions between 6.6.44 and 6.6.57, as well as versions 6.11.x and 6.12-rc1 and 6.12-rc2.

4

What is the impact of CVE-2024-50065?

The impact of CVE-2024-50065 includes the risk of memory pressure leading to unexpected system behavior or denial of service.

5

Is CVE-2024-50065 exploitable remotely?

CVE-2024-50065 is not known to be remotely exploitable; it primarily affects local operations on the affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203