CVE-2023-53508

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

October 1, 2025

Last Modified

January 23, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.43—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-04 10:36 UTCEPSS rescore
  4. 2026-08-03 10:34 UTCEPSS rescore
  5. 2026-08-02 02:25 UTCEPSS rescore
  6. 2026-08-02 02:25 UTCEPSS rescore
  7. 2026-08-01 04:14 UTCEPSS rescore
  8. 2026-07-30 16:26 UTCEPSS rescore
  9. 2026-07-30 01:29 UTCEPSS rescore
  10. 2026-07-28 15:34 UTCEPSS rescore
  11. 2026-07-28 15:34 UTCEPSS rescore
  12. 2026-07-25 14:16 UTCEPSS rescore
  13. 2026-07-24 14:16 UTCEPSS rescore
  14. 2026-07-23 18:41 UTCOSV refresh
  15. 2026-07-23 14:16 UTCEPSS rescore
  16. 2026-07-23 02:29 UTCEG score recompute
  17. 2026-07-22 23:16 UTCEG score recompute
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-22 14:07 UTCEPSS rescore
  20. 2026-07-21 15:23 UTCEPSS rescore
  21. 2026-07-20 17:06 UTCEPSS rescore
  22. 2026-07-19 14:30 UTCEPSS rescore
  23. 2026-07-19 14:29 UTCEPSS rescore
  24. 2026-07-19 02:27 UTCEPSS rescore
  25. 2026-07-19 02:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-18 10:03 UTCEPSS rescore
  2. 2026-07-18 10:03 UTCEPSS rescore
  3. 2026-07-16 17:01 UTCEPSS rescore
  4. 2026-07-15 16:56 UTCEPSS rescore
  5. 2026-07-15 01:59 UTCEPSS rescore
  6. 2026-07-15 01:59 UTCEPSS rescore
  7. 2026-07-13 22:28 UTCEPSS rescore
  8. 2026-07-13 22:28 UTCEPSS rescore
  9. 2026-07-13 06:11 UTCEPSS rescore
  10. 2026-07-12 05:45 UTCEPSS rescore
  11. 2026-07-12 05:45 UTCEPSS rescore
  12. 2026-07-11 08:26 UTCEPSS rescore
  13. 2026-07-09 19:08 UTCEPSS rescore
  14. 2026-07-08 15:13 UTCEPSS rescore
  15. 2026-07-07 13:45 UTCEPSS rescore
  16. 2026-07-07 13:44 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEPSS rescore
  18. 2026-07-06 16:26 UTCEPSS rescore
  19. 2026-07-06 13:11 UTCOSV refresh
  20. 2026-07-05 02:29 UTCEPSS rescore
  21. 2026-07-04 06:29 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-29 14:05 UTCEPSS rescore
  26. 2026-06-28 14:06 UTCEPSS rescore
  27. 2026-06-28 14:06 UTCEPSS rescore
  28. 2026-06-28 04:55 UTCEPSS rescore
  29. 2026-06-27 03:07 UTCEPSS rescore
  30. 2026-06-25 13:48 UTCEPSS rescore
  31. 2026-06-25 13:48 UTCEPSS rescore
  32. 2026-06-24 14:04 UTCEPSS rescore
  33. 2026-06-24 14:04 UTCEPSS rescore
  34. 2026-06-23 21:31 UTCEPSS rescore
  35. 2026-06-23 21:31 UTCEPSS rescore
  36. 2026-06-22 14:24 UTCEPSS rescore
  37. 2026-06-22 14:24 UTCEPSS rescore
  38. 2026-06-21 14:55 UTCEPSS rescore
  39. 2026-06-21 14:55 UTCEPSS rescore
  40. 2026-06-21 01:58 UTCEPSS rescore
  41. 2026-06-21 01:58 UTCEPSS rescore
  42. 2026-06-19 19:24 UTCEPSS rescore
  43. 2026-06-19 19:24 UTCEPSS rescore
  44. 2026-06-18 17:51 UTCEPSS rescore
  45. 2026-06-18 01:14 UTCOSV refresh
  46. 2026-06-17 17:51 UTCEPSS rescore
  47. 2026-06-16 17:51 UTCEPSS rescore
  48. 2026-06-16 17:51 UTCEPSS rescore
  49. 2026-06-15 17:47 UTCEPSS rescore
  50. 2026-06-14 23:16 UTCEPSS rescore
  51. 2026-06-13 22:59 UTCEPSS rescore
  52. 2026-06-13 22:59 UTCEPSS rescore
  53. 2026-06-12 23:11 UTCEPSS rescore
  54. 2026-06-11 13:59 UTCEPSS rescore
  55. 2026-06-10 22:17 UTCEPSS rescore
  56. 2026-06-10 13:21 UTCEPSS rescore
  57. 2026-06-08 14:16 UTCEPSS rescore
  58. 2026-06-08 14:16 UTCEPSS rescore
  59. 2026-06-07 15:24 UTCEPSS rescore
  60. 2026-06-07 15:24 UTCEPSS rescore
  61. 2026-06-06 13:46 UTCEPSS rescore
  62. 2026-06-06 13:46 UTCEPSS rescore
  63. 2026-06-05 22:46 UTCEPSS rescore
  64. 2026-06-05 22:46 UTCEPSS rescore
  65. 2026-06-05 06:09 UTCEPSS rescore
  66. 2026-06-05 06:09 UTCEPSS rescore
  67. 2026-06-04 13:11 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-02 20:12 UTCEPSS rescore
  70. 2026-06-02 20:12 UTCEPSS rescore
  71. 2026-06-01 13:51 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-31 22:30 UTCEPSS rescore
  74. 2026-05-31 00:15 UTCEPSS rescore
  75. 2026-05-31 00:15 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2023-53508?
CVE-2023-53508 is a high vulnerability published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublkctrlstartdev(), if waitforcompletioninterruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLKCMDSTART_DEV, otherwise…
When was CVE-2023-53508 disclosed?
CVE-2023-53508 was first published in the National Vulnerability Database on October 1, 2025, with the most recent update on January 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53508 actively exploited?
CVE-2023-53508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
What is the CVSS score of CVE-2023-53508?
CVE-2023-53508 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53508?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53508, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-53508

Explore →

Is Your Infrastructure Affected by CVE-2023-53508?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs