CVE-2025-39910 json
mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()
published 2025-10-01 13 mo ago modified 2026-10-30 10 d ago also EUVD-2025-32869
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()
kasan_populate_vmalloc() and its helpers ignore the caller's gfp_mask and always allocate memory using the hardcoded GFP_KERNEL flag. This makes them inconsistent with vmalloc(), which was recently extended to support GFP_NOFS and GFP_NOIO allocations.
Page table allocations performed during shadow population also ignore the external gfp_mask. To preserve the intended semantics of GFP_NOFS and GFP_NOIO, wrap the apply_to_page_range() calls into the appropriate memalloc scope.
xfs calls vmalloc with GFP_NOFS, so this bug could lead to deadlock.
There was a report here https://lkml.kernel.org/r/686ea951.050a0220.385921.0016.GAE@google.com
This patch: - Extends kasan_populate_vmalloc() and helpers to take gfp_mask; - Passes gfp_mask down to alloc_pages_bulk() and __get_free_page(); - Enforces GFP_NOFS/NOIO semantics with memalloc_*_save()/restore() around apply_to_page_range(); - Updates vmalloc.c and percpu allocator call sites accordingly.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.16.8, 6.17
- linux Debian 13 6.12.115-2
- linux Debian 14 6.16.8-1
debian advisories DEBIAN-CVE-2025-39910
- git.kernel.org/stable/c/c136f2e4f2edd58a62a3425d4dd373d82834d1f9 commit
- git.kernel.org/stable/c/9598c83a50a5f9d57fd0c12fc08d9425c1ce9537 commit
- git.kernel.org/stable/c/aa1b4b7a1b92743297f9da741424df4703a8e11b commit
- git.kernel.org/stable/c/33b95d90427cb4babf32059e323a6d0c027610fe commit
- git.kernel.org/stable/c/79357cd06d41d0f5a11b17d7c86176e395d10ef2 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-39910 updated cvss 6.2
kernel: mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
- git.kernel.org /stable/c/c136f2e4f2edd58a62a3425d4dd373d82834d1f9
- git.kernel.org /stable/c/9598c83a50a5f9d57fd0c12fc08d9425c1ce9537
- git.kernel.org /stable/c/aa1b4b7a1b92743297f9da741424df4703a8e11b
-
git.kernel.org
/stable/c/33b95d90427cb4babf32059e323a6d0c027610fe
patch
-
git.kernel.org
/stable/c/79357cd06d41d0f5a11b17d7c86176e395d10ef2
patch
Sources
- CVE List CVE-2025-39910
- NVD CVE-2025-39910
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.