CVE-2025-22034: mm/gup: reject FOLL_SPLIT_PMD with hugetlb VMAs
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2e877ff3492267def06dd50cb165dc9ab8838e7d, 48d28417c66cce2f3b0ba773fcb6695a56eff220, 8977752c8056a6a094a279004a49722da15bace3.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 2e877ff3492267def06dd50cb165dc9ab8838e7d, 48d28417c66cce2f3b0ba773fcb6695a56eff220, 8977752c8056a6a094a279004a49722da15bace3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mm/gup: reject FOLL_SPLIT_PMD with hugetlb VMAs Patch series "mm: fixes for device-exclusive entries (hmm)", v2. Discussing the PageTail() call in make_device_exclusive_range() with Willy, I recently discovered [1] that device-exclusive handling does not properly work with THP, making the hmm-tests selftests fail if THPs are enabled on the system. Looking into more details, I found that hugetlb is not properly fenced, and I realized that something that was bugging me for longer -- how device-exclusive entries interact with mapcounts -- completely breaks migration/swapout/split/hwpoison handling of these folios while they have device-exclusive PTEs. The program below can be used to allocate 1 GiB worth of pages and making them device-exclusive on a kernel with CONFIG_TEST_HMM. Once they are device-exclusive, these folios cannot get swapped out (proc$pid/smaps_rollup will always indicate 1 GiB RSS no matter how much one forces memory reclaim), and when having a memory block onlined to ZONE_MOVABLE, trying to offline it will loop forever and complain about failed migration of a page that should be movable. # echo offline > /sys/devices/system/memory/memory136/state # echo online_movable > /sys/devices/system/memory/memory136/state # ./hmm-swap & ... wait until everything is device-exclusive # echo offline > /sys/devices/system/memory/memory136/state [ 285.193431][T14882] page: refcount:2 mapcount:0 mapping:0000000000000000 index:0x7f20671f7 pfn:0x442b6a [ 285.196618][T14882] memcg:ffff888179298000 [ 285.198085][T14882] anon flags: 0x5fff0000002091c(referenced|uptodate| dirty|active|owner_2|swapbacked|node=1|zone=3|lastcpupid=0x7ff) [ 285.201734][T14882] raw: ... [ 285.204464][T14882] raw: ... [ 285.207196][T14882] page dumped because: migration failure [ 285.209072][T14882] page_owner tracks the page as allocated [ 285.210915][T14882] page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), id 14926, tgid 14926 (hmm-swap), ts 254506295376, free_ts 227402023774 [ 285.216765][T14882] post_alloc_hook+0x197/0x1b0 [ 285.218874][T14882] get_page_from_freelist+0x76e/0x3280 [ 285.220864][T14882] __alloc_frozen_pages_noprof+0x38e/0x2740 [ 285.223302][T14882] alloc_pages_mpol+0x1fc/0x540 [ 285.225130][T14882] folio_alloc_mpol_noprof+0x36/0x340 [ 285.227222][T14882] vma_alloc_folio_noprof+0xee/0x1a0 [ 285.229074][T14882] __handle_mm_fault+0x2b38/0x56a0 [ 285.230822][T14882] handle_mm_fault+0x368/0x9f0 ... This series fixes all issues I found so far. There is no easy way to fix without a bigger rework/cleanup. I have a bunch of cleanups on top (some previous sent, some the result of the discussion in v1) that I will send out separately once this landed and I get to it. I wish we could just use some special present PROT_NONE PTEs instead of these (non-present, non-none) fake-swap entries; but that just results in the same problem we keep having (lack of spare PTE bits), and staring at other similar fake-swap entries, that ship has sailed. With this series, make_device_exclusive() doesn't actually belong into mm/rmap.c anymore, but I'll leave moving that for another day. I only tested this series with the hmm-tests selftests due to lack of HW, so I'd appreciate some testing, especially if the interaction between two GPUs wanting a device-exclusive entry works as expected. <program> #include <stdio.h> #include <fcntl.h> #include <stdint.h> #include <unistd.h> #include <stdlib.h> #include <string.h> #include <sys/mman.h> #include <sys/ioctl.h> #include <linux/types.h> #include <linux/ioctl.h> #define HMM_DMIRROR_EXCLUSIVE _IOWR('H', 0x05, struct hmm_dmirror_cmd) struct hmm_dmirror_cmd { __u64 addr; __u64 ptr; __u64 npages; __u64 cpages; __u64 faults; }; const size_t size = 1 * 1024 * 1024 * 1024ul; const size_t chunk_size = 2 * 1024 * 1024ul; int m ---truncated---
- Published
- Apr 16, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.10affected
- 9cb28da54643ad464c47585cd5866c30b0218e67 and later · before 2e877ff3492267def06dd50cb165dc9ab8838e7daffected · git
- 9cb28da54643ad464c47585cd5866c30b0218e67 and later · before 48d28417c66cce2f3b0ba773fcb6695a56eff220affected · git
- 9cb28da54643ad464c47585cd5866c30b0218e67 and later · before fd900832e8440046627b60697687ab5d04398008affected · git
- 9cb28da54643ad464c47585cd5866c30b0218e67 and later · before 8977752c8056a6a094a279004a49722da15bace3affected · git
- before 6.10not affected · semver
- 6.12.23 and later · up to and including 6.12.*not affected · semver
- 6.13.11 and later · up to and including 6.13.*not affected · semver
- 6.14.2 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-22032Apr 16, 2025 · wifi: mt76: mt7921: fix kernel panic due to null pointer dereference22Monitor
- ← EarlierCVE-2025-22033Apr 16, 2025 · arm64: Don't call NULL in do_compat_alignment_fixup()22Monitor
- Later →CVE-2025-22035Apr 16, 2025 · tracing: Fix use-after-free in print_graph_function_flags during tracer switching31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2e877ff3492267def06dd50cb165dc9ab8838e7d | Vendor (CNA) |
| Linux Linux | 48d28417c66cce2f3b0ba773fcb6695a56eff220 | Vendor (CNA) |
| Linux Linux | 8977752c8056a6a094a279004a49722da15bace3 | Vendor (CNA) |
| Linux Linux | fd900832e8440046627b60697687ab5d04398008 | Vendor (CNA) |
| debian:linux | 6.12.25-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.6.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.