CVE-2024-50107

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

platform/x86/intel/pmc: Fix pmc_core_iounmap to call iounmap for valid addresses

Commit 50c6dbdfd16e ("x86/ioremap: Improve iounmap() address range checks") introduces a WARN when adrress ranges of iounmap are invalid. On Thinkpad P1 Gen 7 (Meteor Lake-P) this caused the following warning to appear:

WARNING: CPU: 7 PID: 713 at arch/x86/mm/ioremap.c:461 iounmap+0x58/0x1f0 Modules linked in: rfkill(+) snd_timer(+) fjes(+) snd soundcore intel_pmc_core(+) int3403_thermal(+) int340x_thermal_zone intel_vsec pmt_telemetry acpi_pad pmt_class acpi_tad int3400_thermal acpi_thermal_rel joydev loop nfnetlink zram xe drm_suballoc_helper nouveau i915 mxm_wmi drm_ttm_helper gpu_sched drm_gpuvm drm_exec drm_buddy i2c_algo_bit crct10dif_pclmul crc32_pclmul ttm crc32c_intel polyval_clmulni rtsx_pci_sdmmc ucsi_acpi polyval_generic mmc_core hid_multitouch drm_display_helper ghash_clmulni_intel typec_ucsi nvme sha512_ssse3 video sha256_ssse3 nvme_core intel_vpu sha1_ssse3 rtsx_pci cec typec nvme_auth i2c_hid_acpi i2c_hid wmi pinctrl_meteorlake serio_raw ip6_tables ip_tables fuse CPU: 7 UID: 0 PID: 713 Comm: (udev-worker) Not tainted 6.12.0-rc2iounmap+ #42 Hardware name: LENOVO 21KWCTO1WW/21KWCTO1WW, BIOS N48ET19W (1.06 ) 07/18/2024 RIP: 0010:iounmap+0x58/0x1f0 Code: 85 6a 01 00 00 48 8b 05 e6 e2 28 04 48 39 c5 72 19 eb 26 cc cc cc 48 ba 00 00 00 00 00 00 32 00 48 8d 44 02 ff 48 39 c5 72 23 <0f> 0b 48 83 c4 08 5b 5d 41 5c c3 cc cc cc cc 48 ba 00 00 00 00 00 RSP: 0018:ffff888131eff038 EFLAGS: 00010207 RAX: ffffc90000000000 RBX: 0000000000000000 RCX: ffff888e33b80000 RDX: dffffc0000000000 RSI: ffff888e33bc29c0 RDI: 0000000000000000 RBP: 0000000000000000 R08: ffff8881598a8000 R09: ffff888e2ccedc10 R10: 0000000000000003 R11: ffffffffb3367634 R12: 00000000fe000000 R13: ffff888101d0da28 R14: ffffffffc2e437e0 R15: ffff888110b03b28 FS: 00007f3c1d4b3980(0000) GS:ffff888e33b80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005651cfc93578 CR3: 0000000124e4c002 CR4: 0000000000f70ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace:

? __warn.cold+0xb6/0x176 ? iounmap+0x58/0x1f0 ? report_bug+0x1f4/0x2b0 ? handle_bug+0x58/0x90 ? exc_invalid_op+0x17/0x40 ? asm_exc_invalid_op+0x1a/0x20 ? iounmap+0x58/0x1f0 pmc_core_ssram_get_pmc+0x477/0x6c0 [intel_pmc_core] ? __pfx_pmc_core_ssram_get_pmc+0x10/0x10 [intel_pmc_core] ? __pfx_do_pci_enable_device+0x10/0x10 ? pci_wait_for_pending+0x60/0x110 ? pci_enable_device_flags+0x1e3/0x2e0 ? __pfx_mtl_core_init+0x10/0x10 [intel_pmc_core] pmc_core_ssram_init+0x7f/0x110 [intel_pmc_core] mtl_core_init+0xda/0x130 [intel_pmc_core] ? __mutex_init+0xb9/0x130 pmc_core_probe+0x27e/0x10b0 [intel_pmc_core] ? _raw_spin_lock_irqsave+0x96/0xf0 ? __pfx_pmc_core_probe+0x10/0x10 [intel_pmc_core] ? __pfx_mutex_unlock+0x10/0x10 ? __pfx_mutex_lock+0x10/0x10 ? device_pm_check_callbacks+0x82/0x370 ? acpi_dev_pm_attach+0x234/0x2b0 platform_probe+0x9f/0x150 really_probe+0x1e0/0x8a0 __driver_probe_device+0x18c/0x370 ? __pfx___driver_attach+0x10/0x10 driver_probe_device+0x4a/0x120 __driver_attach+0x190/0x4a0 ? __pfx___driver_attach+0x10/0x10 bus_for_each_dev+0x103/0x180 ? __pfx_bus_for_each_dev+0x10/0x10 ? klist_add_tail+0x136/0x270 bus_add_driver+0x2fc/0x540 driver_register+0x1a5/0x360 ? __pfx_pmc_core_driver_init+0x10/0x10 [intel_pmc_core] do_one_initcall+0xa4/0x380 ? __pfx_do_one_initcall+0x10/0x10 ? kasan_unpoison+0x44/0x70 do_init_module+0x296/0x800 load_module+0x5090/0x6ce0 ? __pfx_load_module+0x10/0x10 ? ima_post_read_file+0x193/0x200 ? __pfx_ima_post_read_file+0x10/0x10 ? rw_verify_area+0x152/0x4c0 ? kernel_read_file+0x257/0x750 ? __pfx_kernel_read_file+0x10/0x10 ? __pfx_filemap_get_read_batch+0x10/0x10 ? init_module_from_file+0xd1/0x130 init_module_from_file+0xd1/0x130 ? __pfx_init_module_from_file+0x10/0 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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 (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
9th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 5, 2024

Last Modified

October 1, 2025

References (2)

Vendor Advisories for CVE-2024-50107(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)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-23ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.11.6 (fixes >=6.8.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.6-1: fixed in 6.11.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 32× 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 90 of 183 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-50107?
CVE-2024-50107 is a medium-severity vulnerability; its CVE record was published on November 5, 2024. In the Linux kernel, the following vulnerability has been resolved: platform/x86/intel/pmc: Fix pmccoreiounmap to call iounmap for valid addresses Commit 50c6dbdfd16e ("x86/ioremap: Improve iounmap() address range checks") introduces a WARN when adrress ranges of iounmap are invalid. On Thinkpad P1…
When was the CVE record for CVE-2024-50107 published?
The CVE record for CVE-2024-50107 was published on November 5, 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 October 1, 2025; the record at its source may have been updated since.
Is CVE-2024-50107 actively exploited?
CVE-2024-50107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50107?
CVE-2024-50107 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50107?
A fix for CVE-2024-50107 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50107 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-50107

Explore →

Is Your Infrastructure Affected by CVE-2024-50107?

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

Book a Demo →Browse All CVEs