CVE-2024-50215

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-11-09. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

November 9, 2024

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4008-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
generic

nvmet-auth: assign dh_key to NULL after kfree_sensitive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e61bd51e44409495d75847e9230736593e4c8710
generic

nvmet-auth: assign dh_key to NULL after kfree_sensitive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2f551b1f72b4c508ab9298419f6feadc3b5d791
generic

nvmet-auth: assign dh_key to NULL after kfree_sensitive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c94e965f766321641ec38e4eece9ce8884543244
generic

nvmet-auth: assign dh_key to NULL after kfree_sensitive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c60af16e1d6cc2237d58336546d6adfc067b6b8f

Vendor Advisories for CVE-2024-50215(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (31 versions)6.1.119-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.11.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.11.7-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 173 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-17 19:27 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:12 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-15 03:08 UTCEPSS rescore
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:59 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-10 09:33 UTCEPSS rescore
  12. 2026-09-08 21:58 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-07 08:18 UTCOSV refresh
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-06 13:46 UTCEPSS rescore
  17. 2026-09-04 13:59 UTCEPSS rescore
  18. 2026-09-04 05:05 UTCEPSS rescore
  19. 2026-09-02 14:10 UTCEPSS rescore
  20. 2026-09-01 13:52 UTCEPSS rescore
  21. 2026-09-01 13:52 UTCEPSS rescore
  22. 2026-09-01 04:37 UTCEPSS rescore
  23. 2026-08-30 19:16 UTCEPSS rescore
  24. 2026-08-30 01:20 UTCEPSS rescore
  25. 2026-08-28 21:39 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:23 UTCEPSS rescore
  2. 2026-08-26 14:44 UTCEPSS rescore
  3. 2026-08-25 13:47 UTCEPSS rescore
  4. 2026-08-24 14:15 UTCEPSS rescore
  5. 2026-08-23 00:18 UTCEPSS rescore
  6. 2026-08-21 23:47 UTCEPSS rescore
  7. 2026-08-20 22:54 UTCEPSS rescore
  8. 2026-08-20 18:01 UTCOSV refresh
  9. 2026-08-19 17:02 UTCEPSS rescore
  10. 2026-08-19 17:02 UTCEPSS rescore
  11. 2026-08-18 13:46 UTCEPSS rescore
  12. 2026-08-17 13:45 UTCEPSS rescore
  13. 2026-08-16 14:54 UTCEPSS rescore
  14. 2026-08-16 02:13 UTCEPSS rescore
  15. 2026-08-15 01:29 UTCEPSS rescore
  16. 2026-08-13 21:59 UTCEPSS rescore
  17. 2026-08-12 13:49 UTCEPSS rescore
  18. 2026-08-11 13:40 UTCEPSS rescore
  19. 2026-08-10 23:58 UTCEPSS rescore
  20. 2026-08-09 13:45 UTCEPSS rescore
  21. 2026-08-08 16:35 UTCEPSS rescore
  22. 2026-08-07 16:25 UTCEPSS rescore
  23. 2026-08-06 13:45 UTCEPSS rescore
  24. 2026-08-05 19:16 UTCEPSS rescore
  25. 2026-08-05 11:54 UTCEG score recompute
  26. 2026-08-05 11:54 UTCVendor advisory
  27. 2026-08-05 11:54 UTCGHSA enrichment
  28. 2026-08-04 15:08 UTCEPSS rescore
  29. 2026-08-04 11:24 UTCEG score recompute
  30. 2026-08-04 11:24 UTCVendor advisory
  31. 2026-08-04 11:24 UTCGHSA enrichment
  32. 2026-08-04 10:36 UTCEPSS rescore
  33. 2026-08-03 10:34 UTCEPSS rescore
  34. 2026-08-02 02:25 UTCEPSS rescore
  35. 2026-08-01 04:14 UTCEPSS rescore
  36. 2026-08-01 04:14 UTCEPSS rescore
  37. 2026-07-31 07:12 UTCOSV refresh
  38. 2026-07-30 16:26 UTCEPSS rescore
  39. 2026-07-30 01:29 UTCEPSS rescore
  40. 2026-07-28 15:35 UTCEPSS rescore
  41. 2026-07-27 14:11 UTCEPSS rescore
  42. 2026-07-26 14:53 UTCEPSS rescore
  43. 2026-07-26 14:53 UTCEPSS rescore
  44. 2026-07-25 14:17 UTCEPSS rescore
  45. 2026-07-25 14:16 UTCEPSS rescore
  46. 2026-07-24 14:16 UTCEPSS rescore
  47. 2026-07-23 14:17 UTCEPSS rescore
  48. 2026-07-23 14:17 UTCEPSS rescore
  49. 2026-07-23 02:42 UTCEG score recompute
  50. 2026-07-22 14:07 UTCEPSS rescore
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-21 15:23 UTCEPSS rescore
  53. 2026-07-20 17:06 UTCEPSS rescore
  54. 2026-07-19 14:30 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-19 02:28 UTCEPSS rescore
  58. 2026-07-18 10:03 UTCEPSS rescore
  59. 2026-07-18 10:03 UTCEPSS rescore
  60. 2026-07-16 17:02 UTCEPSS rescore
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-15 16:56 UTCEPSS rescore
  63. 2026-07-15 01:59 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-13 22:29 UTCEPSS rescore
  66. 2026-07-13 14:38 UTCOSV refresh
  67. 2026-07-13 06:12 UTCEPSS rescore
  68. 2026-07-12 05:45 UTCEPSS rescore
  69. 2026-07-12 05:45 UTCEPSS rescore
  70. 2026-07-11 08:26 UTCEPSS rescore
  71. 2026-07-09 19:09 UTCEPSS rescore
  72. 2026-07-09 19:09 UTCEPSS rescore
  73. 2026-07-08 15:14 UTCEPSS rescore
  74. 2026-07-07 13:45 UTCEPSS rescore
  75. 2026-07-06 16:26 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-50215?
CVE-2024-50215 is a high vulnerability published on November 9, 2024. In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: assign dhkey to NULL after kfreesensitive ctrl->dhkey might be used across multiple calls to nvmetsetup_dhgroup() for the same controller. So it's better to nullify it after release on error path in order to avoid…
When was CVE-2024-50215 disclosed?
CVE-2024-50215 was first published in the National Vulnerability Database on November 9, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50215 actively exploited?
CVE-2024-50215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.3% of all scored CVEs.
What is the CVSS score of CVE-2024-50215?
CVE-2024-50215 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-50215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50215

Explore →

Is Your Infrastructure Affected by CVE-2024-50215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.