CVE-2025-39745
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-11-25
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) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in the Linux kernel's rcutorture testing tool when running on real-time (RT) kernels built with CONFIG_PREEMPT_RT=y. The issue causes a kernel crash (splat) due to incorrect handling of bottom halves (BH) and softirq counts in the preempt_count() during rcutorture_one_extend_check(). The fix involves using softirq_count() to properly check if BH is disabled, preventing the crash.
How can this vulnerability impact me? :
If you are running Linux kernels with real-time preemption (CONFIG_PREEMPT_RT=y) and using the rcutorture testing tool, this vulnerability can cause kernel crashes, leading to system instability or downtime during testing. It primarily affects kernel developers or testers using rcutorture on RT kernels.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for the specific rcutorture_one_extend_check splat messages when running rcutorture tests on kernels built with CONFIG_PREEMPT_RT=y. You can check the kernel log for the following warning message using the command: dmesg | grep rcutorture_one_extend_check
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Linux kernel to a version where the rcutorture_one_extend_check() splat issue in RT kernels has been fixed. Avoid running rcutorture tests on affected kernels until the fix is applied.