CVE-2024-50215·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: assign dh_key to NULL after kfree_sensitive ctrl->dh_key might be used across multiple calls to nvmet_setup_dhgroup() for the same controller. So it's better to nullify it after release on error path in order to avoid double free later in nvmet_destroy_auth(). Found by Linux Verification Center (linuxtesting.org) with Svace.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.11.7
- Published
- 2024-11-09
Affected versions
From: 6.7
Until: 6.11.7
Fixed in: 6.11.7
How to fix this CVE
Update your Linux kernel to version 6.11.7 or later to resolve a memory management flaw in the NVMe authentication subsystem. This vulnerability allows improper handling of Diffie-Hellman key pointers during controller setup, which could lead to double-free conditions and kernel memory corruption. Reboot your system after applying the kernel update to ensure the patched version is active.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r — verify it is 6.11.7 or later
- Confirm NVMe support is enabled: lsmod | grep nvme — look for nvmet_auth module presence
- Search system logs for auth-related errors: sudo grep -i 'nvmet' /var/log/kern.log | grep -i 'error\|double free\|dh_key'
- Verify patch status: sudo dmesg | grep -i 'nvmet\|auth' and compare kernel build date to CVE patch date (kernel >= 6.11.7)
FAQ
What is CVE-2024-50215?
This vulnerability is a use-after-free flaw in the Linux kernel's NVMe authentication module where a Diffie-Hellman key pointer is not properly nullified after deallocation, potentially enabling double-free memory corruption during controller initialization.
Is CVE-2024-50215 being actively exploited?
No. According to CISA's Known Exploited Vulnerabilities (KEV) database, this vulnerability is not currently being actively exploited in the wild, and no public exploits are available.
What versions of Kernel are affected by CVE-2024-50215?
Linux kernel versions 6.7 through 6.11.6 are vulnerable. The vulnerability was fixed in kernel version 6.11.7 and later.
How do I check if my server is vulnerable to CVE-2024-50215?
Run 'uname -r' to display your kernel version. If the output is between 6.7 and 6.11.6, your system is vulnerable. Update to 6.11.7 or later.
Does Defensia detect CVE-2024-50215?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-50215 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/c60af16e1d6cc2237d58336546d6adfc067b6b8f
- https://git.kernel.org/stable/c/c94e965f766321641ec38e4eece9ce8884543244
- https://git.kernel.org/stable/c/d2f551b1f72b4c508ab9298419f6feadc3b5d791
- https://git.kernel.org/stable/c/e61bd51e44409495d75847e9230736593e4c8710
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-50215. Free for 1 server.
Get started free