Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53508

ublk: fail to start device if queue setup is interrupted

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53508, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 71f28f3136aff5890cd56de78abc673f8393cad9 – < 0d5916c439574b18a0734872daa0022b3d6105ad
    • affected 71f28f3136aff5890cd56de78abc673f8393cad9 – < 6ab3e7d424cd413d7a5e976c8a30b4ffa84a65dd
    • affected 71f28f3136aff5890cd56de78abc673f8393cad9 – < 53e7d08f6d6e214c40db1f51291bb2975c789dc2

  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.43 – ≤ 6.1.*
    • unaffected 6.4.8 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53508 badge
[![CVE-2023-53508](https://cveledger.app/badge/CVE-2023-53508.svg)](https://cveledger.app/cve/CVE-2023-53508)

Record last updated .