CVE-2025-38207: mm: fix uprobe pte be overwritten when expanding vma
Vulnerability summary
CVE-2025-38207 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.22% chance of exploitation in the next 30 days, higher than 12.3% of scored vulnerabilities.
Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 5 · Related 4Timeline
- 04-07-2025PublishedVulnerability first disclosed.
- 21-10-2026Last modifiedVulnerability information updated.
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/[email protected]/T/
CVSS metrics
3 scores · 3 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS trend
Probability
0.22%
Chance of exploitation in the next 30 days
Percentile
12%
Versus all other CVEs
30-day change
Increase +0.06 pp
From 0.15% on 21-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu151 products
- linuxAll versions (No fix recorded) | < 6.8.0-151.151
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 6.8.0-1070.76
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Chainguard5 products
- linux-aws-6.12< 6.12.66-r0 | < 6.12.72-r1 | < 6.12.71-r0 | < 6.12.68-r1 | < 6.12.65-r2 | < 6.12.69-r0 | < 6.12.57-r2 | < 6.12.65-r0 | < 6.12.60-r4 | < 6.12.74-r0 | < 6.12.70-r0 | < 6.12.62-r0 | < 6.12.72-r0 | < 6.12.68-r0 | < 6.12.62-r2 | < 6.12.77-r1 | < 6.12.62-r1 | < 6.12.77-r0 | < 6.12.67-r0 | < 6.12.74-r1 | < 6.12.63-r0 | < 6.12.76-r0 | < 6.12.80-r0 | < 6.12.78-r0 | < 6.12.77-r2 | < 6.12.65-r1
- linux-azure-6.12< 6.12.77-r2 | < 6.12.70-r0 | < 6.12.76-r0 | < 6.12.65-r3 | < 6.12.69-r0 | < 6.12.74-r1 | < 6.12.60-r3 | < 6.12.65-r1 | < 6.12.57-r2 | < 6.12.66-r0 | < 6.12.62-r1 | < 6.12.63-r0 | < 6.12.65-r4 | < 6.12.60-r4 | < 6.12.65-r2 | < 6.12.68-r0 | < 6.12.62-r2 | < 6.12.72-r0 | < 6.12.71-r0 | < 6.12.62-r0 | < 6.12.78-r0 | < 6.12.74-r0 | < 6.12.67-r0 | < 6.12.80-r0 | < 6.12.77-r1 | < 6.12.77-r0
- linux-gcp-6.12< 6.12.78-r0 | < 6.12.68-r1 | < 6.12.60-r4 | < 6.12.65-r2 | < 6.12.65-r1 | < 6.12.76-r0 | < 6.12.62-r0 | < 6.12.77-r1 | < 6.12.62-r2 | < 6.12.70-r0 | < 6.12.67-r0 | < 6.12.71-r0 | < 6.12.77-r0 | < 6.12.68-r0 | < 6.12.74-r0 | < 6.12.60-r3 | < 6.12.74-r1 | < 6.12.63-r0 | < 6.12.80-r0 | < 6.12.72-r0 | < 6.12.66-r0 | < 6.12.62-r1 | < 6.12.69-r0 | < 6.12.77-r2 | < 6.12.65-r0 | < 6.12.57-r2
- linux-qemu-6.12< 6.12.77-r0 | < 6.12.65-r1 | < 6.12.77-r2 | < 6.12.71-r0 | < 6.12.76-r0 | < 6.12.70-r0 | < 6.12.68-r0 | < 6.12.72-r0 | < 6.12.69-r0 | < 6.12.67-r0 | < 6.12.65-r2 | < 6.12.66-r0 | < 6.12.77-r1 | < 6.12.78-r0 | < 6.12.80-r0 | < 6.12.74-r1 | < 6.12.74-r0
- linux-vmware-6.12< 6.12.74-r0 | < 6.12.78-r0 | < 6.12.71-r0 | < 6.12.68-r0 | < 6.12.77-r1 | < 6.12.76-r0 | < 6.12.66-r0 | < 6.12.65-r2 | < 6.12.65-r1 | < 6.12.80-r0 | < 6.12.77-r2 | < 6.12.68-r1 | < 6.12.69-r0 | < 6.12.67-r0 | < 6.12.72-r0 | < 6.12.70-r0 | < 6.12.77-r0 | < 6.12.74-r1
Debian2 products
- linuxAll versions (No fix recorded) | < 6.12.115-2 | < 6.16.3-1
- linux-6.12< 6.12.115-2~deb12u1
Linux2 products
- linux≥ 2b144498350860b6ee9dc57ff27a93ad488de5dc, < 7030046a9b4de8199a3cbc3de20366d95dce2142 | ≥ 2b144498350860b6ee9dc57ff27a93ad488de5dc, < 58b83b9a9a929611a2a2e7d88f45cb0d786b7ee0 | ≥ 2b144498350860b6ee9dc57ff27a93ad488de5dc, < 2b12d06c37fd3a394376f42f026a7478d826ed63 | 3.5
- linux_kernel≥ 3.5, < 6.15.4
4 vendors · 160 products