Vulnerability · CVE-2025-38029
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context apply_to_pte_range() enters the lazy MMU…
Published Jun 18, 2025 · catalog updated Oct 21, 2026 · linux kernel
Check if you run it
No confirmed exploitation is on record for CVE-2025-38029. EPSS is 0.16%. Act only if a listed version of linux kernel is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.16%
- Remediation
- Version ranges on file
- Affected products
- cpe linux/linux kernel
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context apply_to_pte_range() enters the lazy MMU mode and then invokes kasan_populate_vmalloc_pte() callback on each page table walk iteration. However, the callback can go into sleep when trying to allocate a single page, e.g. if an architecutre disables preemption on lazy MMU mode enter. On s390 if make arch_enter_lazy_mmu_mode() -> preempt_enable() and arch_leave_lazy_mmu_mode() -> preempt_disable(), such crash occurs: [ 0.663336] BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:321 [ 0.663348] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd [ 0.663358] preempt_count: 1, expected: 0 [ 0.663366] RCU nest depth: 0, expected: 0 [ 0.663375] no locks held by kthreadd/2. [ 0.663383] Preemption disabled at: [ 0.663386] [ ] apply_to_pte_range+0xfa/0x4a0 [ 0.663405] CPU: 0 UID: 0 PID: 2 Comm: kthreadd Not tainted 6.15.0-rc5-gcc-kasan-00043-gd76bb1ebb558-dirty #162 PREEMPT [ 0.663408] Hardware name: IBM 3931 A01 701 (KVM/Linux) [ 0.663409] Call Trace: [ 0.663410] [ ] dump_stack_lvl+0xe8/0x140 [ 0.663413] [ ] __might_resched+0x66e/0x700 [ 0.663415] [ ] __alloc_frozen_pages_noprof+0x370/0x4b0 [ 0.663419] [ ] alloc_pages_mpol+0x1a0/0x4a0 [ 0.663421] [ ] alloc_frozen_pages_noprof+0x88/0xc0 [ 0.663424] [ ] alloc_pages_noprof+0x22/0x120 [ 0.663427] [ ] get_free_pages_noprof+0x2c/0xc0 [ 0.663429] [ ] kasan_populate_vmalloc_pte+0x50/0x120 [ 0.663433] [ ] apply_to_pte_range+0x118/0x4a0 [ 0.663435] [ ] apply_to_pmd_range+0x194/0x3e0 [ 0.663437] [ ] __apply_to_page_range+0x2fe/0x7a0 [ 0.663440] [ ] apply_to_page_range+0x28/0x40 [ 0.663442] [ ] kasan_populate_vmalloc+0x82/0xa0 [ 0.663445] [ ] alloc_vmap_area+0x34c/0xc10 [ 0.663448] [ ] __get_vm_area_node+0x186/0x2a0 [ 0.663451] [ ] __vmalloc_node_range_noprof+0x116/0x310 [ 0.663454] [ ] __vmalloc_node_noprof+0xd0/0x110 [ 0.663457] [ ] alloc_thread_stack_node+0xf
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe linux/linux kernel6.15
- cpe linux/linux kernel< 6.14.9
How to fix CVE-2025-38029
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-38029. EPSS is 0.16%. Act only if a listed version of linux kernel is installed.
Which versions are affected?
Compare what you have installed with linux/linux kernel 6.15; linux/linux kernel < 6.14.9. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.16%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jun 18, 2025 · NIST NVD
Detected
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context apply_to_pte_range() enters the lazy MMU mode and then invokes kasan_populate_vmalloc_pte() callback on each page table walk iteration. However, the callback can go into sleep when trying to allocate a single page, e.g. if an architecutre disables preemption on lazy MMU mo
Oct 21, 2026 · NIST NVD
Updated
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context apply_to_pte_range() enters the lazy MMU mode and then invokes kasan_populate_vmalloc_pte() callback on each page table walk iteration. However, the callback can go into sleep when trying to allocate a single page, e.g. if an architecutre disables preemption on lazy MMU mo
Sources
- CVE.orgVulnerability recordCVE-2025-38029
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-38029
30-day exploitation probability 0.16%
first.org - NIST NVDVulnerability recordCVE-2025-38029
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context apply_to_pte_range() enters the lazy MMU mode and then invokes kasan_populate_vmalloc_pte() callback on each page table walk iteration. However, the c
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.