CVE-2024-50014: ext4: fix access to uninitialised lock in fc replay path
ext4: fix access to uninitialised lock in fc replay path
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 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 - Compensating control
If you are affected, the trace indicates the kernel splat/lockdep report is triggered in the ext4 fast-commit replay path; as a compensating step, you can turn off the locking correctness validator as indicated by the message: “turning off the locking correctness validator.”
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50014?
CVE-2024-50014 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-50014?
To address CVE-2024-50014, upgrade to the latest kernel versions such as 6.1.128-1 or 6.12.15-1.
Which versions of the Linux kernel are affected by CVE-2024-50014?
CVE-2024-50014 affects Linux kernel versions prior to 6.10.14 and those between 6.11 and 6.11.3.
What systems are impacted by CVE-2024-50014?
Systems running Debian or other Linux distributions with vulnerable kernel versions are impacted by CVE-2024-50014.
What exploits are associated with CVE-2024-50014?
CVE-2024-50014 can potentially lead to denial of service or security issues when exploiting the uninitialized lock in the ext4 filesystem.