CVE-2023-53151
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-11-24
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 | 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 | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's md/raid10 subsystem where there is no limit on raid1/raid10 plugged bio operations. Specifically, during flush writes, raid1 calls cond_resched() to yield the CPU, but raid10 does not. This can cause too many writes to accumulate and lead to a soft lockup, where the CPU gets stuck for an extended period. The issue was fixed by adding cond_resched() to raid10 similar to raid1 to prevent the CPU from being stuck.
How can this vulnerability impact me? :
This vulnerability can cause a soft lockup in the system's CPU during heavy write operations on raid10 devices. This means the CPU can become unresponsive or stuck for a long time, leading to degraded system performance, increased IO latency, and potentially impacting system stability during intensive disk write workloads.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing soft lockup warnings related to raid10 devices in the system logs. For example, messages like 'watchdog: BUG: soft lockup - CPU#X stuck for Ys! [md0_raid10:PID]' indicate the issue. You can monitor the kernel logs using commands such as 'dmesg | grep -i soft lockup' or 'journalctl -k | grep -i soft lockup'. Additionally, running writeback tests on raid10 devices with ramdisks may reproduce the soft lockup condition.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the fix has been applied, which adds cond_resched() calls to raid10 to prevent soft lockups during flush writes. Until the update is applied, monitoring for soft lockup warnings and avoiding heavy writeback loads on raid10 devices can reduce the risk. Note that the underlying issue is related to unlimited plugged bio and may require kernel optimization.