CVE-2023-53531
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-10-02
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) |
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 race condition in the Linux kernel's null_blk driver related to poll request timeout handling. When performing an io_uring benchmark on /dev/nullb0, if poll requests timeout, it can cause a kernel crash due to a NULL pointer dereference. The issue arises from a race between two functions, null_timeout_rq() and null_poll(), which manipulate poll request lists without proper synchronization. The fix involves setting the request state to MQ_RQ_COMPLETE under a lock to safely detect and handle the race, preventing kernel panic.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (kernel panic) when certain timeout conditions occur during io_uring operations on /dev/nullb0. Such crashes can lead to system instability, downtime, and potential data loss or service interruption on affected systems.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch that fixes the kernel panic caused by the null_blk poll request timeout handling race condition. This patch sets the request state to MQ_RQ_COMPLETE under nq->poll_lock protection, preventing the race between null_timeout_rq() and null_poll().