| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025111258-CVE-2025-40153-c820@gregkh> Date: Wed, 12 Nov 2025 19:24:29 +0900 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: avoid soft lockup when mprotect to large memory area When calling mprotect() to a large hugetlb memory area in our customer's workload (~300GB hugetlb memory), soft lockup was observed: watchdog: BUG: soft lockup - CPU#98 stuck for 23s! [t2_new_sysv:126916] CPU: 98 PID: 126916 Comm: t2_new_sysv Kdump: loaded Not tainted 6.17-rc7 Hardware name: GIGACOMPUTING R2A3-T40-AAV1/Jefferson CIO, BIOS 5.4.4.1 07/15/2025 pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : mte_clear_page_tags+0x14/0x24 lr : mte_sync_tags+0x1c0/0x240 sp : ffff80003150bb80 x29: ffff80003150bb80 x28: ffff00739e9705a8 x27: 0000ffd2d6a00000 x26: 0000ff8e4bc00000 x25: 00e80046cde00f45 x24: 0000000000022458 x23: 0000000000000000 x22: 0000000000000004 x21: 000000011b380000 x20: ffff000000000000 x19: 000000011b379f40 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc875e0aa5e2c x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : fffffc01ce7a5c00 x4 : 00000000046cde00 x3 : fffffc0000000000 x2 : 0000000000000004 x1 : 0000000000000040 x0 : ffff0046cde7c000 Call trace: mte_clear_page_tags+0x14/0x24 set_huge_pte_at+0x25c/0x280 hugetlb_change_protection+0x220/0x430 change_protection+0x5c/0x8c mprotect_fixup+0x10c/0x294 do_mprotect_pkey.constprop.0+0x2e0/0x3d4 __arm64_sys_mprotect+0x24/0x44 invoke_syscall+0x50/0x160 el0_svc_common+0x48/0x144 do_el0_svc+0x30/0xe0 el0_svc+0x30/0xf0 el0t_64_sync_handler+0xc4/0x148 el0t_64_sync+0x1a4/0x1a8 Soft lockup is not triggered with THP or base page because there is cond_resched() called for each PMD size. Although the soft lockup was triggered by MTE, it should be not MTE specific. The other processing which takes long time in the loop may trigger soft lockup too. So add cond_resched() for hugetlb to avoid soft lockup. The Linux kernel CVE team has assigned CVE-2025-40153 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 5.4.301 with commit 30498c44c2a0b20f6833ed7d8fc3df901507f760 Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 5.10.246 with commit 5783485ab2be06be5312b26c8793526edc09123d Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 5.15.195 with commit 547e123e9d342a44c756446640ed847a8aeec611 Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 6.1.156 with commit 957faf9582f92bb2be8ebe4ab6aa1c2bc71d9859 Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 6.6.112 with commit 964598e6f70a1be9fe675280bf16b4f96b0a6809 Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 6.12.53 with commit 4975c975ed9457a77953a26aeef85fdba7cf5498 Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 6.17.3 with commit c6096f3947f68f96defedb8764b3b1ca4cf3469f Issue introduced in 2.6.17 with commit 8f860591ffb29738cf5539b6fbf27f50dcdeb380 and fixed in 6.18-rc1 with commit f52ce0ea90c83a28904c7cc203a70e6434adfecb Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-40153 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: mm/hugetlb.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/30498c44c2a0b20f6833ed7d8fc3df901507f760 https://git.kernel.org/stable/c/5783485ab2be06be5312b26c8793526edc09123d https://git.kernel.org/stable/c/547e123e9d342a44c756446640ed847a8aeec611 https://git.kernel.org/stable/c/957faf9582f92bb2be8ebe4ab6aa1c2bc71d9859 https://git.kernel.org/stable/c/964598e6f70a1be9fe675280bf16b4f96b0a6809 https://git.kernel.org/stable/c/4975c975ed9457a77953a26aeef85fdba7cf5498 https://git.kernel.org/stable/c/c6096f3947f68f96defedb8764b3b1ca4cf3469f https://git.kernel.org/stable/c/f52ce0ea90c83a28904c7cc203a70e6434adfecb
Powered by blists - more mailing lists