CVE-2024-50221

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-45156 (ENISA EUVD) · GHSA-9fm7-prpc-h7x8 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/amd/pm: Vangogh: Fix kernel memory out of bounds write

KASAN reports that the GPU metrics table allocated in vangogh_tables_init() is not large enough for the memset done in smu_cmn_init_soft_gpu_metrics(). Condensed report follows:

[ 33.861314] BUG: KASAN: slab-out-of-bounds in smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu] [ 33.861799] Write of size 168 at addr ffff888129f59500 by task mangoapp/1067 ... [ 33.861808] CPU: 6 UID: 1000 PID: 1067 Comm: mangoapp Tainted: G W 6.12.0-rc4 #356 1a56f59a8b5182eeaf67eb7cb8b13594dd23b544 [ 33.861816] Tainted: [W]=WARN [ 33.861818] Hardware name: Valve Galileo/Galileo, BIOS F7G0107 12/01/2023 [ 33.861822] Call Trace: [ 33.861826] [ 33.861829] dump_stack_lvl+0x66/0x90 [ 33.861838] print_report+0xce/0x620 [ 33.861853] kasan_report+0xda/0x110 [ 33.862794] kasan_check_range+0xfd/0x1a0 [ 33.862799] __asan_memset+0x23/0x40 [ 33.862803] smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.863306] vangogh_get_gpu_metrics_v2_4+0x123/0xad0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.864257] vangogh_common_get_gpu_metrics+0xb0c/0xbc0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.865682] amdgpu_dpm_get_gpu_metrics+0xcc/0x110 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.866160] amdgpu_get_gpu_metrics+0x154/0x2d0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.867135] dev_attr_show+0x43/0xc0 [ 33.867147] sysfs_kf_seq_show+0x1f1/0x3b0 [ 33.867155] seq_read_iter+0x3f8/0x1140 [ 33.867173] vfs_read+0x76c/0xc50 [ 33.867198] ksys_read+0xfb/0x1d0 [ 33.867214] do_syscall_64+0x90/0x160 ... [ 33.867353] Allocated by task 378 on cpu 7 at 22.794876s: [ 33.867358] kasan_save_stack+0x33/0x50 [ 33.867364] kasan_save_track+0x17/0x60 [ 33.867367] __kasan_kmalloc+0x87/0x90 [ 33.867371] vangogh_init_smc_tables+0x3f9/0x840 [amdgpu] [ 33.867835] smu_sw_init+0xa32/0x1850 [amdgpu] [ 33.868299] amdgpu_device_init+0x467b/0x8d90 [amdgpu] [ 33.868733] amdgpu_driver_load_kms+0x19/0xf0 [amdgpu] [ 33.869167] amdgpu_pci_probe+0x2d6/0xcd0 [amdgpu] [ 33.869608] local_pci_probe+0xda/0x180 [ 33.869614] pci_device_probe+0x43f/0x6b0

Empirically we can confirm that the former allocates 152 bytes for the table, while the latter memsets the 168 large block.

Root cause appears that when GPU metrics tables for v2_4 parts were added it was not considered to enlarge the table to fit.

The fix in this patch is rather "brute force" and perhaps later should be done in a smarter way, by extracting and consolidating the part version to size logic to a common helper, instead of brute forcing the largest possible allocation. Nevertheless, for now this works and fixes the out of bounds write.

v2: * Drop impossible v3_0 case. (Mario)

(cherry picked from commit 0880f58f9609f0200483a49429af0f050d281703)

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
15th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 9, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

drm/amd/pm: Vangogh: Fix kernel memory out of bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4aa923a6e6406b43566ef6ac35a3d9a3197fa3e8
Web page

drm/amd/pm: Vangogh: Fix kernel memory out of bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8fd9f0d57af4f8f48b383ec28287af85b47cb9f
Web page

drm/amd/pm: Vangogh: Fix kernel memory out of bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2024-50221(1)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-27ubuntu
linuxKernel @ 6.6.63 (fixes >=6.6.0)—osv

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 rangeFix by version rangeDependents
linux—
  • every version up to 6.11.7-1: fixed in 6.11.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.7-1: fixed in 6.11.7-1
—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 221 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-50221?
CVE-2024-50221 is a high-severity vulnerability; its CVE record was published on November 9, 2024. In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Vangogh: Fix kernel memory out of bounds write KASAN reports that the GPU metrics table allocated in vangogh_tables_init() is not large enough for the memset done in smu_cmn_init_soft_gpu_metrics(). Condensed report…
When was the CVE record for CVE-2024-50221 published?
The CVE record for CVE-2024-50221 was published on November 9, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-50221 actively exploited?
CVE-2024-50221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50221?
CVE-2024-50221 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-50221?
A fix for CVE-2024-50221 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50221 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-50221?

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

Book a Demo →Browse All CVEs