{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40153 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40153 is a denial of service vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40153 and fix it if it is affected.\n\nWhat it is: CVE-2025-40153 is a denial of service vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40153 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40153/ (Markdown: https://insights.sbomify.com/CVE-2025-40153/index.md)","id":"CVE-2025-40153","markdown":"https://insights.sbomify.com/CVE-2025-40153/index.md","name":"CVE-2025-40153","record":{"aliases":["BELL-CVE-2025-40153","DEBIAN-CVE-2025-40153","GHSA-vxqq-p97q-mvpj","ROOT-OS-DEBIAN-11-CVE-2025-40153","ROOT-OS-DEBIAN-13-CVE-2025-40153","ROOT-OS-UBUNTU-2404-CVE-2025-40153","UBUNTU-CVE-2025-40153"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a soft lockup and system hang by calling mprotect on a large hugetlb memory area, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: hugetlb: avoid soft lockup when mprotect to large memory area\n\nWhen calling mprotect() to a large hugetlb memory area in our customer's\nworkload (~300GB hugetlb memory), soft lockup was observed:\n\nwatchdog: BUG: soft lockup - CPU#98 stuck for 23s! [t2_new_sysv:126916]\n\nCPU: 98 PID: 126916 Comm: t2_new_sysv Kdump: loaded Not tainted 6.17-rc7\nHardware name: GIGACOMPUTING R2A3-T40-AAV1/Jefferson CIO, BIOS 5.4.4.1 07/15/2025\npstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : mte_clear_page_tags+0x14/0x24\nlr : mte_sync_tags+0x1c0/0x240\nsp : ffff80003150bb80\nx29: ffff80003150bb80 x28: ffff00739e9705a8 x27: 0000ffd2d6a00000\nx26: 0000ff8e4bc00000 x25: 00e80046cde00f45 x24: 0000000000022458\nx23: 0000000000000000 x22: 0000000000000004 x21: 000000011b380000\nx20: ffff000000000000 x19: 000000011b379f40 x18: 0000000000000000\nx17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\nx14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\nx11: 0000000000000000 x10: 0000000000000000 x9 : ffffc875e0aa5e2c\nx8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000\nx5 : fffffc01ce7a5c00 x4 : 00000000046cde00 x3 : fffffc0000000000\nx2 : 0000000000000004 x1 : 0000000000000040 x0 : ffff0046cde7c000\n\nCall trace:\n  mte_clear_page_tags+0x14/0x24\n  set_huge_pte_at+0x25c/0x280\n  hugetlb_change_protection+0x220/0x430\n  change_protection+0x5c/0x8c\n  mprotect_fixup+0x10c/0x294\n  do_mprotect_pkey.constprop.0+0x2e0/0x3d4\n  __arm64_sys_mprotect+0x24/0x44\n  invoke_syscall+0x50/0x160\n  el0_svc_common+0x48/0x144\n  do_el0_svc+0x30/0xe0\n  el0_svc+0x30/0xf0\n  el0t_64_sync_handler+0xc4/0x148\n  el0t_64_sync+0x1a4/0x1a8\n\nSoft lockup is not triggered with THP or base page because there is\ncond_resched() called for each PMD size.\n\nAlthough the soft lockup was triggered by MTE, it should be not MTE\nspecific.  The other processing which takes long time in the loop may\ntrigger soft lockup too.\n\nSo add cond_resched() for hugetlb to avoid soft lockup.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mm: hugetlb: avoid soft lockup when mprotect to large memory area","id":"CVE-2025-40153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping","id":"CVE-2025-40154"},"packages":[],"prev":{"headline":"drm/msm: Fix bootup splat with separate_gpu_drm modparam","id":"CVE-2025-40152"},"products":["Linux"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can cause a soft lockup and system hang by calling mprotect on a large hugetlb memory area, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-40153/"}