CVE-2023-53291
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-03
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.6 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.121 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.39 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.13 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.4 (exc) |
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 occurs in the Linux kernel's rcuscale module where the kfree_scale_thread thread(s) continue running even after the rcuscale module has been unloaded. This leads to a kernel crash (splat) due to a page fault when the running thread tries to access memory that is no longer valid. The issue is fixed by ensuring that the kfree_scale_cleanup() function is called during the removal of the rcuscale module, stopping the thread(s) properly.
How can this vulnerability impact me? :
This vulnerability can cause a kernel crash (splat) resulting in system instability or downtime. If the rcuscale module is unloaded while the kfree_scale_thread thread(s) are still running, it can lead to a page fault and kernel panic, potentially disrupting normal system operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running the 'kfree_rcu_test' test case with the rcuscale module loaded and then unloading the module to observe if a kernel crash (splat) occurs. The suggested commands are: 1. modprobe rcuscale kfree_rcu_test=1 2. After some time, run: rmmod rcuscale 3. Then run: rmmod torture If the system experiences a kernel BUG or page fault similar to the described splat, the vulnerability is present.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the fix that stops the kfree_scale_thread thread(s) after unloading the rcuscale module. This is done by ensuring the kernel includes the patch that invokes kfree_scale_cleanup() from rcu_scale_cleanup() when removing the rcuscale module. Until the fix is applied, avoid unloading the rcuscale module after running the kfree_rcu_test to prevent kernel crashes.