Answer in brief
CVE-2024-50215 records a Unknown severity vulnerability in nvmet-auth: assign dh_key to NULL after kfree_sensitive. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <c94e965f766321641ec38e4eece9ce8884543244 || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <c60af16e1d6cc2237d58336546d6adfc067b6b8f || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <e61bd51e44409495d75847e9230736593e4c8710 || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <d2f551b1f72b4c508ab9298419f6feadc3b5d791 | c94e965f766321641ec38e4eece9ce8884543244, c60af16e1d6cc2237d58336546d6adfc067b6b8f, e61bd51e44409495d75847e9230736593e4c8710, d2f551b1f72b4c508ab9298419f6feadc3b5d791 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Nov 9, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50215 records a Unknown severity vulnerability in nvmet-auth: assign dh_key to NULL after kfree_sensitive. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <c94e965f766321641ec38e4eece9ce8884543244 || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <c60af16e1d6cc2237d58336546d6adfc067b6b8f || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <e61bd51e44409495d75847e9230736593e4c8710 || >=7a277c37d3522e9b2777d762bbbcecafae2b1f8d <d2f551b1f72b4c508ab9298419f6feadc3b5d791 | c94e965f766321641ec38e4eece9ce8884543244, c60af16e1d6cc2237d58336546d6adfc067b6b8f, e61bd51e44409495d75847e9230736593e4c8710, d2f551b1f72b4c508ab9298419f6feadc3b5d791 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Nov 9, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.