CVE-2024-50020

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-10-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ice: Fix improper handling of refcount in ice_sriov_set_msix_vec_count()

This patch addresses an issue with improper reference count handling in the ice_sriov_set_msix_vec_count() function.

First, the function calls ice_get_vf_by_id(), which increments the reference count of the vf pointer. If the subsequent call to ice_get_vf_vsi() fails, the function currently returns an error without decrementing the reference count of the vf pointer, leading to a reference count leak. The correct behavior, as implemented in this patch, is to decrement the reference count using ice_put_vf(vf) before returning an error when vsi is NULL.

Second, the function calls ice_sriov_get_irqs(), which sets vf->first_vector_idx. If this call returns a negative value, indicating an error, the function returns an error without decrementing the reference count of the vf pointer, resulting in another reference count leak. The patch addresses this by adding a call to ice_put_vf(vf) before returning an error when vf->first_vector_idx < 0.

This bug was identified by an experimental static analysis tool developed by our team. The tool specializes in analyzing reference count operations and identifying potential mismanagement of reference counts. In this case, the tool flagged the missing decrement operation as a potential issue, leading to this patch.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

October 21, 2024

Last Modified

October 25, 2024

Patch Availability(15)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.11.4-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.11.4-1

All Vendor Advisories

(14)

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 163 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-50020?
CVE-2024-50020 is a medium vulnerability published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: ice: Fix improper handling of refcount in icesriovsetmsixvec_count() This patch addresses an issue with improper reference count handling in the icesriovsetmsixvec_count() function. First, the function calls icegetvfbyid(), which…
When was CVE-2024-50020 disclosed?
CVE-2024-50020 was first published in the National Vulnerability Database on October 21, 2024, with the most recent update on October 25, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50020 actively exploited?
CVE-2024-50020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.2% of all scored CVEs.
What is the CVSS score of CVE-2024-50020?
CVE-2024-50020 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50020, 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-50020

Explore →

Is Your Infrastructure Affected by CVE-2024-50020?

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