Release Date: | 2024-05-01 |
In the Linux kernel, the following vulnerability has been resolved:\nmm/memory-failure: fix deadlock when hugetlb_optimize_vmemmap is enabled\nWhen I did hard offline test with hugetlb pages, below deadlock occurs:\n======================================================\nWARNING: possible circular locking dependency detected\n6.8.0-11409-gf6cef5f8c37f #1 Not tainted\n------------------------------------------------------\nbash/46904 is trying to acquire lock:\nffffffffabe68910 (cpu_hotplug_lock){++++}-{0:0}, at: static_key_slow_dec+0x16/0x60\nbut task is already holding lock:\nffffffffabf92ea8 (pcp_batch_high_lock){+.+.}-{3:3}, at: zone_pcp_disable+0x16/0x40\nwhich lock already depends on the new lock.\nthe existing dependency chain (in reverse order) is:\n-> #1 (pcp_batch_high_lock){+.+.}-{3:3}:\n__mutex_lock+0x6c/0x770\npage_alloc_cpu_online+0x3c/0x70\ncpuhp_invoke_callback+0x397/0x5f0\n__cpuhp_invoke_callback_range+0x71/0xe0\n_cpu_up+0xeb/0x210\ncpu_up+0x91/0xe0\ncpuhp_bringup_mask+0x49/0xb0\nbringup_nonboot_cpus+0xb7/0xe0\nsmp_init+0x25/0xa0\nkernel_init_freeable+0x15f/0x3e0\nkernel_init+0x15/0x1b0\nret_from_fork+0x2f/0x50\nret_from_fork_asm+0x1a/0x30\n-> #0 (cpu_hotplug_lock){++++}-{0:0}:\n__lock_acquire+0x1298/0x1cd0\nlock_acquire+0xc0/0x2b0\ncpus_read_lock+0x2a/0xc0\nstatic_key_slow_dec+0x16/0x60\n__hugetlb_vmemmap_restore_folio+0x1b9/0x200\ndissolve_free_huge_page+0x211/0x260\n__page_handle_poison+0x45/0xc0\nmemory_failure+0x65e/0xc70\nhard_offline_page_store+0x55/0xa0\nkernfs_fop_write_iter+0x12c/0x1d0\nvfs_write+0x387/0x550\nksys_write+0x64/0xe0\ndo_syscall_64+0xca/0x1e0\nentry_SYSCALL_64_after_hwframe+0x6d/0x75\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0 CPU1\n---- ----\nlock(pcp_batch_high_lock);\nlock(cpu_hotplug_lock);\nlock(pcp_batch_high_lock);\nrlock(cpu_hotplug_lock);\n*** DEADLOCK ***\n5 locks held by bash/46904:\n#0: ffff98f6c3bb23f0 (sb_writers#5){.+.+}-{0:0}, at: ksys_write+0x64/0xe0\n#1: ffff98f6c328e488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0xf8/0x1d0\n#2: ffff98ef83b31890 (kn->active#113){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x100/0x1d0\n#3: ffffffffabf9db48 (mf_mutex){+.+.}-{3:3}, at: memory_failure+0x44/0xc70\n#4: ffffffffabf92ea8 (pcp_batch_high_lock){+.+.}-{3:3}, at: zone_pcp_disable+0x16/0x40\nstack backtrace:\nCPU: 10 PID: 46904 Comm: bash Kdump: loaded Not tainted 6.8.0-11409-gf6cef5f8c37f #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\nCall Trace:\n
See more information about CVE-2024-26987 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.1 metrics and score provided are preliminary and subject to review.
Base Score: | 5.5 | CVSS Vector: | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Attack Vector: | Local network | Attack Complexity: | Low |
Privileges Required: | Low | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | None |
Integrity Impact: | None | Availability Impact: | High |
Platform | Errata | Release Date |
Oracle Linux version 8 (kernel-uek) | ELSA-2024-12815 | 2024-11-11 |
Oracle Linux version 9 (kernel) | ELSA-2024-9315 | 2024-11-14 |
Oracle Linux version 9 (kernel-uek) | ELSA-2024-12815 | 2024-11-11 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections: