Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2023-53531

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: null_blk: fix poll request timeout handling When doing io_uring benchmark on /dev/nullb0, it's easy to crash the kernel if poll…

Published Oct 1, 2025CWE-476EPSS 0.15%

Overview

CVE-2023-53531 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

null_blk: fix poll request timeout handling

When doing io_uring benchmark on /dev/nullb0, it's easy to crash the

kernel if poll requests timeout triggered, as reported by David. [1]

BUG: kernel NULL pointer dereference, address: 0000000000000008

Workqueue: kblockd blk_mq_timeout_work

RIP: 0010:null_timeout_rq+0x4e/0x91

Call Trace:

? null_timeout_rq+0x4e/0x91

blk_mq_handle_expired+0x31/0x4b

bt_iter+0x68/0x84

? bt_tags_iter+0x81/0x81

__sbitmap_for_each_set.constprop.0+0xb0/0xf2

? __blk_mq_complete_request_remote+0xf/0xf

bt_for_each+0x46/0x64

? __blk_mq_complete_request_remote+0xf/0xf

? percpu_ref_get_many+0xc/0x2a

blk_mq_queue_tag_busy_iter+0x14d/0x18e

blk_mq_timeout_work+0x95/0x127

process_one_work+0x185/0x263

worker_thread+0x1b5/0x227

This is indeed a race problem between null_timeout_rq() and null_poll().

null_poll() null_timeout_rq()

spin_lock(&nq->poll_lock)

list_splice_init(&nq->poll_list,

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/5a26e45edb4690d58406178b5a9ea4c6dcf2c105Refgit.kernel.org/stable/c/a0b4a0666beacfe8add9c71d8922475541dbae73Refgit.kernel.org/stable/c/a7cb2e709f2927cc3c76781df3e45de2381b3b9d

How CyberStrike helps

Frequently asked questions

What is CVE-2023-53531?

CVE-2023-53531 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2023-53531?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53531?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53531?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53531 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2023

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999