CVE-2025-40153

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

November 12, 2025

Last Modified

April 15, 2026

References (8)

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-05-21ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1064 (5.15.0-1064.68) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-05-21ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-21ubuntu
linuxKernel @ 5.4.301—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-08-04 15:09 UTCEPSS rescore
  2. 2026-08-04 10:37 UTCEPSS rescore
  3. 2026-08-03 10:35 UTCEPSS rescore
  4. 2026-08-02 02:26 UTCEPSS rescore
  5. 2026-08-01 04:15 UTCEPSS rescore
  6. 2026-07-30 16:27 UTCEPSS rescore
  7. 2026-07-30 01:29 UTCEPSS rescore
  8. 2026-07-28 15:35 UTCEPSS rescore
  9. 2026-07-27 07:09 UTCOSV refresh
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-23 02:55 UTCEG score recompute
  13. 2026-07-22 14:07 UTCEPSS rescore
  14. 2026-07-22 14:07 UTCEPSS rescore
  15. 2026-07-21 15:24 UTCEPSS rescore
  16. 2026-07-20 17:07 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 14:30 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-19 02:28 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-16 17:02 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 01:59 UTCEPSS rescore
  2. 2026-07-15 01:59 UTCEPSS rescore
  3. 2026-07-13 22:29 UTCEPSS rescore
  4. 2026-07-13 22:29 UTCEPSS rescore
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 01:47 UTCOSV refresh
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-09 19:09 UTCEPSS rescore
  12. 2026-07-07 13:45 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 04:55 UTCEPSS rescore
  27. 2026-06-28 04:55 UTCEPSS rescore
  28. 2026-06-27 03:08 UTCEPSS rescore
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-24 14:04 UTCEPSS rescore
  33. 2026-06-24 14:04 UTCEPSS rescore
  34. 2026-06-23 21:32 UTCEPSS rescore
  35. 2026-06-23 21:32 UTCEPSS rescore
  36. 2026-06-22 14:25 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-21 14:56 UTCEPSS rescore
  39. 2026-06-21 14:56 UTCEPSS rescore
  40. 2026-06-21 12:31 UTCOSV refresh
  41. 2026-06-21 01:59 UTCEPSS rescore
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-19 19:25 UTCEPSS rescore
  44. 2026-06-19 19:25 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-17 17:52 UTCEPSS rescore
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-14 23:17 UTCEPSS rescore
  51. 2026-06-13 23:00 UTCEPSS rescore
  52. 2026-06-12 23:11 UTCEPSS rescore
  53. 2026-06-11 14:00 UTCEPSS rescore
  54. 2026-06-10 22:18 UTCEPSS rescore
  55. 2026-06-10 13:22 UTCEPSS rescore
  56. 2026-06-08 14:16 UTCEPSS rescore
  57. 2026-06-08 14:16 UTCEPSS rescore
  58. 2026-06-07 15:24 UTCEPSS rescore
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 13:47 UTCEPSS rescore
  61. 2026-06-05 22:46 UTCEPSS rescore
  62. 2026-06-05 22:46 UTCEPSS rescore
  63. 2026-06-05 06:10 UTCEPSS rescore
  64. 2026-06-05 06:10 UTCEPSS rescore
  65. 2026-06-02 20:12 UTCEPSS rescore
  66. 2026-06-02 06:09 UTCOSV refresh
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-28 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2025-40153?
CVE-2025-40153 is a publicly disclosed vulnerability published on November 12, 2025. 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 -…
When was CVE-2025-40153 disclosed?
CVE-2025-40153 was first published in the National Vulnerability Database on November 12, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40153 actively exploited?
CVE-2025-40153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.8% of all scored CVEs.
How do I remediate CVE-2025-40153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40153, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-40153

Explore →

Is Your Infrastructure Affected by CVE-2025-40153?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs