# CVE-2025-39843: mm: slub: avoid wake up kswapd in set_track_prepare > A lock recursion deadlock in the Linux kernel SLUB allocator can cause a system crash when debug objects are enabled. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Sep 2025 - **Updated:** 12 May 2026 - **Also known as:** ALSA-2025:21926, BELL-CVE-2025-39843, DEBIAN-CVE-2025-39843, GHSA-fwr4-vx34-qhjp, RHSA-2025:21926, RLSA-2025:21926, ROOT-OS-DEBIAN-12-CVE-2025-39843, ROOT-OS-DEBIAN-13-CVE-2025-39843, ROOT-OS-UBUNTU-2404-CVE-2025-39843, UBUNTU-CVE-2025-39843 ## What is CVE-2025-39843? CVE-2025-39843 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the Linux kernel, the following vulnerability has been resolved: mm: slub: avoid wake up kswapd in set_track_prepare set_track_prepare() can incur lock recursion. The issue is that it is called from hrtimer_start_range_ns holding the per_cpu(hrtimer_bases)[n].lock, but when enabled CONFIG_DEBUG_OBJECTS_TIMERS, may wake up kswapd in set_track_prepare, and try to hold the per_cpu(hrtimer_bases)[n].lock. Avoid deadlock caused by implicitly waking up kswapd by passing in allocation flags, which do not contain __GFP_KSWAPD_RECLAIM in the debug_objects_fill_pool() case. Inside stack depot they are processed by gfp_nested_mask(). Since ___slab_alloc() has preemption disabled, we mask out __GFP_DIRECT_RECLAIM from the flags there. The oops looks something like: BUG: spinlock recursion on CPU#3, swapper/3/0 lock: 0xffffff8a4bf29c80, .magic: dead4ead, .owner: swapper/3/0, .owner_cpu: 3 Hardware name: Qualcomm Technologies, Inc. Popsicle based on SM8850 (DT) Call trace: spin_bug+0x0 _raw_spin_lock_irqsave+0x80 hrtimer_try_to_cancel+0x94 task_contending+0x10c enqueue_dl_entity+0x2a4 dl_server_start+0x74 enqueue_task_fair+0x568 enqueue_task+0xac do_activate_task+0x14c ttwu_do_activate+0xcc try_to_wake_up+0x6c8 default_wake_function+0x20 autoremove_wake_function+0x1c __wake_up+0xac wakeup_kswapd+0x19c wake_all_kswapds+0x78 __alloc_pages_slowpath+0x1ac __alloc_pages_noprof+0x298 stack_depot_save_flags+0x6b0 stack_depot_save+0x14 set_track_prepare+0x5c ___slab_alloc+0xccc __kmalloc_cache_noprof+0x470 __set_page_owner+0x2bc post_alloc_hook[jt]+0x1b8 prep_new_page+0x28 get_page_from_freelist+0x1edc __alloc_pages_noprof+0x13c alloc_slab_page+0x244 allocate_slab+0x7c ___slab_alloc+0x8e8 kmem_cache_alloc_noprof+0x450 debug_objects_fill_pool+0x22c debug_object_activate+0x40 enqueue_hrtimer[jt]+0xdc hrtimer_start_range_ns+0x5f8 ... Weakness: CWE-667 (Improper Locking) ## Which versions are affected by CVE-2025-39843? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-core` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-core` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-devel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-devel-matched` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-modules` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-modules-extra` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-devel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-devel-matched` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-modules-extra` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-abi-stablelists` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-debug-devel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-debug-devel-matched` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-devel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-devel-matched` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-doc` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-headers` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-zfcpdump-devel` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-zfcpdump-devel-matched` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `perf` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `python3-perf` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `rtla` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `rv` | AlmaLinux:9 | All versions | 5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-64k-debug-devel-matched` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-64k-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-64k-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-64k-devel-matched` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debug-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debug-devel-matched` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debuginfo-common-aarch64` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debuginfo-common-ppc64le` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debuginfo-common-s390x` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | | `kernel-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.14.0-611.9.1.el9_7 | Products: Debian Debian Linux, Linux kernel. ## How do I fix CVE-2025-39843? Apply the vendor's patch. ## Is CVE-2025-39843 being exploited? There is no known exploitation of CVE-2025-39843 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-39843 and fix it if it is affected. What it is: CVE-2025-39843 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-39843 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-39843/ (Markdown: https://insights.sbomify.com/CVE-2025-39843/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-39843 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-39843 - OSV: https://osv.dev/vulnerability/CVE-2025-39843 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-39843/ Summaries are generated and may contain mistakes; the official description above is the record.