CVE-2025-39754
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-11-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.17 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's memory management code, specifically between the smaps_hugetlb_range() function and the migration process. The smaps_hugetlb_range() function handles page table entries (pte) without holding the page table lock (ptl), which can concurrently occur with page migration operations. This race can lead to a kernel BUG_ON error in pfn_swap_entry_to_page(), causing system instability or crashes. The fix involves holding the ptl lock in smaps_hugetlb_range() to prevent this race.
How can this vulnerability impact me? :
This vulnerability can cause system instability or crashes due to a race condition in memory management. If exploited or triggered, it may lead to kernel panics or unexpected behavior, potentially resulting in denial of service or data loss on affected Linux systems.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch that fixes the race condition in smaps_hugetlb_range by holding the ptl lock as described. This involves updating the Linux kernel to a version where this issue is resolved.