CVE-2024-50215
nvmet-auth: assign dh_key to NULL after kfree_sensitive
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
nvmet-auth: assign dh_key to NULL after kfree_sensitive
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.
Reserved 2024-10-21 | Published 2024-11-09 | Updated 2024-11-19 | Assigner Linuxgit.kernel.org/...c/c94e965f766321641ec38e4eece9ce8884543244
git.kernel.org/...c/c60af16e1d6cc2237d58336546d6adfc067b6b8f
git.kernel.org/...c/e61bd51e44409495d75847e9230736593e4c8710
git.kernel.org/...c/d2f551b1f72b4c508ab9298419f6feadc3b5d791
Support options
