CVE-2025-40153 json
mm: hugetlb: avoid soft lockup when mprotect to large memory area
published 2025-11-12 11 mo ago modified 2026-10-19 20 d ago also EUVD-2025-124930
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, 6.18
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40153
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
ubuntu advisories UBUNTU-CVE-2025-40153
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1.21.16
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.28.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.28.1
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0316-1SUSE-SU-2026:0315-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.8.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-kvmsmall openSUSE Leap 16.0 6.12.0-160000.8.1
opensuse advisories openSUSE-SU-2025:20172-1
- git.kernel.org/stable/c/30498c44c2a0b20f6833ed7d8fc3df901507f760 commit
- git.kernel.org/stable/c/5783485ab2be06be5312b26c8793526edc09123d commit
- git.kernel.org/stable/c/547e123e9d342a44c756446640ed847a8aeec611 commit
- git.kernel.org/stable/c/957faf9582f92bb2be8ebe4ab6aa1c2bc71d9859 commit
- git.kernel.org/stable/c/964598e6f70a1be9fe675280bf16b4f96b0a6809 commit
- git.kernel.org/stable/c/4975c975ed9457a77953a26aeef85fdba7cf5498 commit
- git.kernel.org/stable/c/c6096f3947f68f96defedb8764b3b1ca4cf3469f commit
- git.kernel.org/stable/c/f52ce0ea90c83a28904c7cc203a70e6434adfecb commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-40153 updated cvss 5.5
kernel: Linux kernel: Denial of Service via mprotect() on huge transparent huge pages
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/30498c44c2a0b20f6833ed7d8fc3df901507f760
- git.kernel.org /stable/c/5783485ab2be06be5312b26c8793526edc09123d
- git.kernel.org /stable/c/547e123e9d342a44c756446640ed847a8aeec611
- git.kernel.org /stable/c/957faf9582f92bb2be8ebe4ab6aa1c2bc71d9859
- git.kernel.org /stable/c/964598e6f70a1be9fe675280bf16b4f96b0a6809
- git.kernel.org /stable/c/4975c975ed9457a77953a26aeef85fdba7cf5498
- git.kernel.org /stable/c/c6096f3947f68f96defedb8764b3b1ca4cf3469f
- git.kernel.org /stable/c/f52ce0ea90c83a28904c7cc203a70e6434adfecb
Sources
- CVE List CVE-2025-40153
- NVD CVE-2025-40153
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.