CVE-2023-54242
Division by Zero Vulnerability in Linux Kernel BFQ Block Scheduler
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.2.1 |
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 division by zero error in the Linux kernel's block layer, specifically in the bfq (Budget Fair Queueing) scheduler. When the weighted sum (wsum) is zero, the calculation of a limit causes a division by zero, leading to a kernel crash (oops). The issue occurs during I/O priority stress testing and has been fixed by skipping the problematic calculation when wsum is zero.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a division by zero error, potentially leading to system instability or denial of service. It can disrupt normal system operations, especially under certain I/O priority stress conditions, affecting availability.
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 division by zero errors related to bfq (Budget Fair Queueing) block scheduler. Specifically, look for kernel oops messages similar to 'divide error' or stack traces involving 'bfqq_request_over_limit'. Running the command 'dmesg | grep -i divide' or 'journalctl -k | grep -i divide' may help identify such errors. Additionally, running the stress test command 'stress-ng --ioprio 0' as root can reproduce the issue if the system is vulnerable.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this division by zero error in the bfq block scheduler is fixed. Avoid running the 'stress-ng --ioprio 0' test or similar I/O priority stress tests until the kernel is patched. Monitoring kernel logs for related errors and applying vendor-provided kernel updates is recommended.