Vulnerability · Published Jul 4, 2025 · Assigned by Linux

CVE-2025-38207mm: fix uprobe pte be overwritten when expanding vma

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 88.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: mm: fix uprobe pte be overwritten when expanding vma Patch series "Fix uprobe pte be overwritten when expanding vma". This patch (of 4): We encountered a BUG alert triggered by Syzkaller as follows: BUG: Bad rss-counter state mm:00000000b4a60fca type:MM_ANONPAGES val:1 And we can reproduce it with the following steps: 1. register uprobe on file at zero offset 2. mmap the file at zero offset: addr1 = mmap(NULL, 2 * 4096, PROT_NONE, MAP_PRIVATE, fd, 0); 3. mremap part of vma1 to new vma2: addr2 = mremap(addr1, 4096, 2 * 4096, MREMAP_MAYMOVE); 4. mremap back to orig addr1: mremap(addr2, 4096, 4096, MREMAP_MAYMOVE | MREMAP_FIXED, addr1); In step 3, the vma1 range [addr1, addr1 + 4096] will be remap to new vma2 with range [addr2, addr2 + 8192], and remap uprobe anon page from the vma1 to vma2, then unmap the vma1 range [addr1, addr1 + 4096]. In step 4, the vma2 range [addr2, addr2 + 4096] will be remap back to the addr range [addr1, addr1 + 4096]. Since the addr range [addr1 + 4096, addr1 + 8192] still maps the file, it will take vma_merge_new_range to expand the range, and then do uprobe_mmap in vma_complete. Since the merged vma pgoff is also zero offset, it will install uprobe anon page to the merged vma. However, the upcomming move_page_tables step, which use set_pte_at to remap the vma2 uprobe pte to the merged vma, will overwrite the newly uprobe pte in the merged vma, and lead that pte to be orphan. Since the uprobe pte will be remapped to the merged vma, we can remove the unnecessary uprobe_mmap upon merged vma. This problem was first found in linux-6.6.y and also exists in the community syzkaller: https://lore.kernel.org/all/000000000000ada39605a5e71711@google.com/T/

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2025-38207
Debian:13linux6.12.115-2DEBIAN-CVE-2025-38207
Debian:14linux6.16.3-1DEBIAN-CVE-2025-38207
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2025-38207
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2025-38207
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2025-38207

Affected products (as reported)

VendorProductVersions
Linux Linux 2b144498350860b6ee9dc57ff27a93ad488de5dc – before 7030046a9b4de8199a3cbc3de20366d95dce21422b144498350860b6ee9dc57ff27a93ad488de5dc – before 58b83b9a9a929611a2a2e7d88f45cb0d786b7ee02b144498350860b6ee9dc57ff27a93ad488de5dc – before 2b12d06c37fd3a394376f42f026a7478d826ed63
Linux Linux 3.5

References