CVE-2021-47552

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2021-34554 (ENISA EUVD)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release()

For avoiding to slow down queue destroy, we don't call blk_mq_quiesce_queue() in blk_cleanup_queue(), instead of delaying to cancel dispatch work in blk_release_queue().

However, this way has caused kernel oops[1], reported by Changhui. The log shows that scsi_device can be freed before running blk_release_queue(), which is expected too since scsi_device is released after the scsi disk is closed and the scsi_device is removed.

Fixes the issue by canceling blk-mq dispatch work in both blk_cleanup_queue() and disk_release():

1) when disk_release() is run, the disk has been closed, and any sync dispatch activities have been done, so canceling dispatch work is enough to quiesce filesystem I/O dispatch activity.

2) in blk_cleanup_queue(), we only focus on passthrough request, and passthrough request is always explicitly allocated & freed by its caller, so once queue is frozen, all sync dispatch activity for passthrough request has been done, then it is enough to just cancel dispatch work for avoiding any dispatch activity.

[1] kernel panic log [12622.769416] BUG: kernel NULL pointer dereference, address: 0000000000000300 [12622.777186] #PF: supervisor read access in kernel mode [12622.782918] #PF: error_code(0x0000) - not-present page [12622.788649] PGD 0 P4D 0 [12622.791474] Oops: 0000 [#1] PREEMPT SMP PTI [12622.796138] CPU: 10 PID: 744 Comm: kworker/10:1H Kdump: loaded Not tainted 5.15.0+ #1 [12622.804877] Hardware name: Dell Inc. PowerEdge R730/0H21J3, BIOS 1.5.4 10/002/2015 [12622.813321] Workqueue: kblockd blk_mq_run_work_fn [12622.818572] RIP: 0010:sbitmap_get+0x75/0x190 [12622.823336] Code: 85 80 00 00 00 41 8b 57 08 85 d2 0f 84 b1 00 00 00 45 31 e4 48 63 cd 48 8d 1c 49 48 c1 e3 06 49 03 5f 10 4c 8d 6b 40 83 f0 01 <48> 8b 33 44 89 f2 4c 89 ef 0f b6 c8 e8 fa f3 ff ff 83 f8 ff 75 58 [12622.844290] RSP: 0018:ffffb00a446dbd40 EFLAGS: 00010202 [12622.850120] RAX: 0000000000000001 RBX: 0000000000000300 RCX: 0000000000000004 [12622.858082] RDX: 0000000000000006 RSI: 0000000000000082 RDI: ffffa0b7a2dfe030 [12622.866042] RBP: 0000000000000004 R08: 0000000000000001 R09: ffffa0b742721334 [12622.874003] R10: 0000000000000008 R11: 0000000000000008 R12: 0000000000000000 [12622.881964] R13: 0000000000000340 R14: 0000000000000000 R15: ffffa0b7a2dfe030 [12622.889926] FS: 0000000000000000(0000) GS:ffffa0baafb40000(0000) knlGS:0000000000000000 [12622.898956] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [12622.905367] CR2: 0000000000000300 CR3: 0000000641210001 CR4: 00000000001706e0 [12622.913328] Call Trace: [12622.916055] [12622.918394] scsi_mq_get_budget+0x1a/0x110 [12622.922969] __blk_mq_do_dispatch_sched+0x1d4/0x320 [12622.928404] ? pick_next_task_fair+0x39/0x390 [12622.933268] __blk_mq_sched_dispatch_requests+0xf4/0x140 [12622.939194] blk_mq_sched_dispatch_requests+0x30/0x60 [12622.944829] __blk_mq_run_hw_queue+0x30/0xa0 [12622.949593] process_one_work+0x1e8/0x3c0 [12622.954059] worker_thread+0x50/0x3b0 [12622.958144] ? rescuer_thread+0x370/0x370 [12622.962616] kthread+0x158/0x180 [12622.966218] ? set_kthread_struct+0x40/0x40 [12622.970884] ret_from_fork+0x22/0x30 [12622.974875] [12622.977309] Modules linked in: scsi_debug rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs sunrpc dm_multipath intel_rapl_msr intel_rapl_common dell_wmi_descriptor sb_edac rfkill video x86_pkg_temp_thermal intel_powerclamp dcdbas coretemp kvm_intel kvm mgag200 irqbypass i2c_algo_bit rapl drm_kms_helper ipmi_ssif intel_cstate intel_uncore syscopyarea sysfillrect sysimgblt fb_sys_fops pcspkr cec mei_me lpc_ich mei ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter drm fuse xfs libcrc32c sr_mod cdrom sd_mod t10_pi sg ixgbe ahci libahci crct10dif_pclmul crc32_pclmul crc32c_intel libata megaraid_sas ghash_clmulni_intel tg3 wdat_w ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

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

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 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 SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 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 Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

May 24, 2024

Last Modified

August 5, 2026

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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 97 of 192 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-47552?
CVE-2021-47552 is a medium-severity vulnerability; its CVE record was published on May 24, 2024. In the Linux kernel, the following vulnerability has been resolved: blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release() For avoiding to slow down queue destroy, we don't call blk_mq_quiesce_queue() in blk_cleanup_queue(), instead of delaying to cancel dispatch work in…
When was the CVE record for CVE-2021-47552 published?
The CVE record for CVE-2021-47552 was published on May 24, 2024. 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2021-47552 actively exploited?
CVE-2021-47552 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47552?
CVE-2021-47552 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-47552?
A fix for CVE-2021-47552 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-47552

Explore →

Is Your Infrastructure Affected by CVE-2021-47552?

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