CVE-2025-38084
Last modified
CVE-2025-38084 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: unshare page tables during VMA split, not before Currently, __split_vma() triggers hugetlb page table unsharing through vm_ops->may_split(). This happens before the VMA lock and rmap locks are taken - which is too early, it allows racing VMA-locked page faults in our process and racing rmap walks from other processes to cause page tables to be shared again before we actually perform the split. Fix it by explicitly calling into the hugetlb unshare logic from __split_vma() in the same place where THP splitting also happens. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: unshare page tables during VMA split, not before Currently, __split_vma() triggers hugetlb page table unsharing through vm_ops->may_split(). This happens before the VMA lock and rmap locks are taken - which is too early, it allows racing VMA-locked page faults in our process and racing rmap walks from other processes to cause page tables to be shared again before we actually perform the split. Fix it by explicitly calling into the hugetlb unshare logic from __split_vma() in the same place where THP splitting also happens. At that point, both the VMA and the rmap(s) are write-locked. An annoying detail is that we can now call into the helper hugetlb_unshare_pmds() from two different locking contexts: 1. from hugetlb_split(), holding: - mmap lock (exclusively) - VMA lock - file rmap lock (exclusively) 2. hugetlb_unshare_all_pmds(), which I think is designed to be able to call us with only the mmap lock held (in shared mode), but currently only runs while holding mmap lock (exclusively) and VMA lock Backporting note: This commit fixes a racy protection that was introduced in commit b30c14cd6102 ("hugetlb: unshare some PMDs when splitting VMAs"); that commit claimed to fix an issue introduced in 5.13, but it should actually also go all the way back. [jannh@google.com: v2]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.20, < 5.10.239 |
| Linux | Linux Kernel | >= 5.11, < 5.15.186 |
| Linux | Linux Kernel | >= 5.16, < 6.1.142 |
| Linux | Linux Kernel | >= 6.2, < 6.6.95 |
| Linux | Linux Kernel | >= 6.7, < 6.12.35 |
| Linux | Linux Kernel | >= 6.13, < 6.15.4 |
| Debian | Debian Linux | 11.0 |
References
- https://project-zero.issues.chromium.org/issues/420715744Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38084?
How severe is CVE-2025-38084?
How do I fix CVE-2025-38084?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38079In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-3808A vulnerability has been found in zhenfeng13 My-BBS 1.0 and …6.5
- CVE-2025-38080In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38081In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38082In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38083In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38085In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38086In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38087In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38088In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38089In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3809The Debug Log Manager plugin for WordPress is vulnerable to …7.2
Are you affected by CVE-2025-38084?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
