CVE-2023-53508Linux vulnerability

5 documents5 sources
Severity
7.8HIGHNVD
EPSS
0.0%
top 98.19%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedOct 1

Description

In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublk_ctrl_start_dev(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_START_DEV, otherwise kernel oops can be triggered. Reported by German when working on qemu-storage-deamon which requires single thread ublk daemon.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitability: 1.8 | Impact: 5.9

Affected Packages4 packages

NVDlinux/linux_kernel6.06.1.43+2
Debianlinux/linux_kernel< 6.1.52-1+2
CVEListV5linux/linux71f28f3136aff5890cd56de78abc673f8393cad90d5916c439574b18a0734872daa0022b3d6105ad+3
debiandebian/linux< linux 6.1.52-1 (bookworm)

Patches

🔴Vulnerability Details

2
OSV
CVE-2023-53508: In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublk_ctrl_start_dev(),2025-10-01
GHSA
GHSA-f7fj-8w72-h36h: In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublk_ctrl_start_dev(2025-10-01

📋Vendor Advisories

2
Red Hat
kernel: ublk: fail to start device if queue setup is interrupted2025-10-01
Debian
CVE-2023-53508: linux - In the Linux kernel, the following vulnerability has been resolved: ublk: fail ...2023