🛡️ CVE-2024-50107 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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:

<TASK>

? __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---

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-50107 is recorded against 2 packages.

  • kernel (from 6.8.0 up to 6.11.6)
  • linux-kernel

Timeline and source

Published on 5 November 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-50107 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-11-05
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.8.0 6.11.6
linux-kernel

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-50107 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024