First published: Sat Nov 09 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.0<6.1.116 | |
Linux Kernel | >=6.2<6.6.60 | |
Linux Kernel | >=6.7<6.11.7 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 | |
Linux Kernel | =6.12-rc4 | |
Linux Kernel | =6.12-rc5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-50215 has a moderate severity level due to potential information leakage and denial of service risks.
To fix CVE-2024-50215, update your Linux kernel to a version that includes the patch, specifically versions after 6.1.116, 6.6.60, or 6.11.7.
CVE-2024-50215 affects Linux kernel versions from 6.0 up to 6.1.116, from 6.2 up to 6.6.60, and from 6.7 up to 6.11.7, including specific release candidates.
CVE-2024-50215 impacts components related to the nvmet-auth function in the Linux kernel, particularly during the handling of the dh_key.
Yes, CVE-2024-50215 is a common vulnerability found across various Linux distributions that utilize affected kernel versions.