CVE-2024-50245: fs/ntfs3: Fix possible deadlock in mi_read
fs/ntfs3: Fix possible deadlock in miread
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.64.2-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.15.173.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50245?
CVE-2024-50245 has not been assigned a CVSS score yet, but it addresses a potential deadlock issue in the Linux kernel.
How do I fix CVE-2024-50245?
To fix CVE-2024-50245, update the Linux kernel to a version that incorporates the relevant patches provided by the kernel maintainers.
Which Linux kernel versions are affected by CVE-2024-50245?
CVE-2024-50245 affects various versions of the Linux kernel between 5.15.x and 6.12.x.
Is CVE-2024-50245 a critical vulnerability in Linux?
While CVE-2024-50245 may not appear critical, it could lead to deadlocks, impacting system performance and reliability.
What systems are at risk due to CVE-2024-50245?
Systems running affected versions of the Linux kernel are at risk, particularly those using the NTFS file system.