CVE-2025-39866
BaseFortify
Publication date: 2025-09-19
Last updated on: 2025-12-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.1.153 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in the Linux kernel's __mark_inode_dirty() function. It occurs due to a race condition when __mark_inode_dirty() accesses a bdi_writeback structure that is in the process of being switched and freed. The root cause involves improper locking around inode and writeback structures, leading to the use of memory that has already been freed. The fix involves holding the inode spinlock until the delayed writeback wakeup function finishes, preventing the race condition.
How can this vulnerability impact me? :
This vulnerability can lead to use-after-free memory corruption in the Linux kernel, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code with kernel privileges. This can compromise the security and reliability of systems running vulnerable Linux kernel versions.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by updating the Linux kernel to a version that includes the patch for the use-after-free issue in __mark_inode_dirty(). Immediate mitigation involves applying the kernel update that holds the inode spinlock until wb_wakeup_delayed() finishes, preventing the race condition.