CVE-2023-53508

High

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.

Package Linux Kernel
Published 2025-10-01
Last modified 2026-01-23
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

7.8

out of 10
High
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.0 and later are affected. Fixed in 6.1.43, 6.4.8, 6.5 and their respective stable series.

Affected from
≥ 6.0
Fixed in
✓ 6.1.43 6.1.x ✓ 6.4.8 6.4.x ✓ 6.5

References

The following references provide additional information about CVE-2023-53508 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2023-53508?

    CVE-2023-53508 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.0 onward and has been patched in 6.1.43, 6.4.8 and 6.5. CVE-2023-53508 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2023-53508?

    CVE-2023-53508 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H .

  • Is there a patch available for CVE-2023-53508?

    Yes — CVE-2023-53508 has been patched. Fixed versions include 6.1.43, 6.4.8 and 6.5. If you are running Linux kernel 6.0 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2023-53508 actively exploited?

    No — CVE-2023-53508 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.