CVE-2023-53730

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week

Also known asEUVD-2023-59998 (ENISA EUVD) · GHSA-qcg4-xxf6-m8j4 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost

adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before invoking it.

Fix it by using spin_lock_irqsave() instead, which can keep IRQ state consistent with before when unlock.

================================ WARNING: inconsistent lock state 5.10.0-02758-g8e5f91fd772f #26 Not tainted -------------------------------- inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390 {IN-HARDIRQ-W} state was registered at: __lock_acquire+0x3d7/0x1070 lock_acquire+0x197/0x4a0 __raw_spin_lock_irqsave _raw_spin_lock_irqsave+0x3b/0x60 bfq_idle_slice_timer_body bfq_idle_slice_timer+0x53/0x1d0 __run_hrtimer+0x477/0xa70 __hrtimer_run_queues+0x1c6/0x2d0 hrtimer_interrupt+0x302/0x9e0 local_apic_timer_interrupt __sysvec_apic_timer_interrupt+0xfd/0x420 run_sysvec_on_irqstack_cond sysvec_apic_timer_interrupt+0x46/0xa0 asm_sysvec_apic_timer_interrupt+0x12/0x20 irq event stamp: 837522 hardirqs last enabled at (837521): [] __raw_spin_unlock_irqrestore hardirqs last enabled at (837521): [] _raw_spin_unlock_irqrestore+0x3d/0x40 hardirqs last disabled at (837522): [] __raw_spin_lock_irq hardirqs last disabled at (837522): [] _raw_spin_lock_irq+0x43/0x50 softirqs last enabled at (835852): [] __do_softirq+0x558/0x8ec softirqs last disabled at (835845): [] asm_call_irq_on_stack+0xf/0x20

other info that might help us debug this: Possible unsafe locking scenario:

CPU0 ---- lock(&bfqd->lock); lock(&bfqd->lock);

* DEADLOCK *

3 locks held by kworker/2:3/388: #0: ffff888107af0f38 ((wq_completion)kthrotld){+.+.}-{0:0}, at: process_one_work+0x742/0x13f0 #1: ffff8881176bfdd8 ((work_completion)(&td->dispatch_work)){+.+.}-{0:0}, at: process_one_work+0x777/0x13f0 #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390

stack backtrace: CPU: 2 PID: 388 Comm: kworker/2:3 Not tainted 5.10.0-02758-g8e5f91fd772f #26 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: kthrotld blk_throtl_dispatch_work_fn Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x167 print_usage_bug valid_state mark_lock_irq.cold+0x32/0x3a mark_lock+0x693/0xbc0 mark_held_locks+0x9e/0xe0 __trace_hardirqs_on_caller lockdep_hardirqs_on_prepare.part.0+0x151/0x360 trace_hardirqs_on+0x5b/0x180 __raw_spin_unlock_irq _raw_spin_unlock_irq+0x24/0x40 spin_unlock_irq adjust_inuse_and_calc_cost+0x4fb/0x970 ioc_rqos_merge+0x277/0x740 __rq_qos_merge+0x62/0xb0 rq_qos_merge bio_attempt_back_merge+0x12c/0x4a0 blk_mq_sched_try_merge+0x1b6/0x4d0 bfq_bio_merge+0x24a/0x390 __blk_mq_sched_bio_merge+0xa6/0x460 blk_mq_sched_bio_merge blk_mq_submit_bio+0x2e7/0x1ee0 __submit_bio_noacct_mq+0x175/0x3b0 submit_bio_noacct+0x1fb/0x270 blk_throtl_dispatch_work_fn+0x1ef/0x2b0 process_one_work+0x83e/0x13f0 process_scheduled_works worker_thread+0x7e3/0xd80 kthread+0x353/0x470 ret_from_fork+0x1f/0x30

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2025

Last Modified

October 28, 2026

Vendor Advisories for CVE-2023-53730(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.10.188 (fixes >=5.10.0)—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 224 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2023-53730?
CVE-2023-53730 is a vulnerability whose severity is not yet rated; its CVE record was published on October 22, 2025. In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before…
When was the CVE record for CVE-2023-53730 published?
The CVE record for CVE-2023-53730 was published on October 22, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 28, 2026; the record at its source may have been updated since.
Is CVE-2023-53730 actively exploited?
CVE-2023-53730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2023-53730?
A fix for CVE-2023-53730 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53730 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53730

Explore →

Is Your Infrastructure Affected by CVE-2023-53730?

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