CVE-2021-47178

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-03-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
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.6%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

scsi: target: core: Avoid smp_processor_id() in preemptible code

The BUG message "BUG: using smp_processor_id() in preemptible [00000000] code" was observed for TCMU devices with kernel config DEBUG_PREEMPT.

The message was observed when blktests block/005 was run on TCMU devices with fileio backend or user:zbc backend [1]. The commit 1130b499b4a7 ("scsi: target: tcm_loop: Use LIO wq cmd submission helper") triggered the symptom. The commit modified work queue to handle commands and changed 'current->nr_cpu_allowed' at smp_processor_id() call.

The message was also observed at system shutdown when TCMU devices were not cleaned up [2]. The function smp_processor_id() was called in SCSI host work queue for abort handling, and triggered the BUG message. This symptom was observed regardless of the commit 1130b499b4a7 ("scsi: target: tcm_loop: Use LIO wq cmd submission helper").

To avoid the preemptible code check at smp_processor_id(), get CPU ID with raw_smp_processor_id() instead. The CPU ID is used for performance improvement then thread move to other CPU will not affect the code.

[1]

[ 56.468103] run blktests block/005 at 2021-05-12 14:16:38 [ 57.369473] check_preemption_disabled: 85 callbacks suppressed [ 57.369480] BUG: using smp_processor_id() in preemptible [00000000] code: fio/1511 [ 57.369506] BUG: using smp_processor_id() in preemptible [00000000] code: fio/1510 [ 57.369512] BUG: using smp_processor_id() in preemptible [00000000] code: fio/1506 [ 57.369552] caller is __target_init_cmd+0x157/0x170 [target_core_mod] [ 57.369606] CPU: 4 PID: 1506 Comm: fio Not tainted 5.13.0-rc1+ #34 [ 57.369613] Hardware name: System manufacturer System Product Name/PRIME Z270-A, BIOS 1302 03/15/2018 [ 57.369617] Call Trace: [ 57.369621] BUG: using smp_processor_id() in preemptible [00000000] code: fio/1507 [ 57.369628] dump_stack+0x6d/0x89 [ 57.369642] check_preemption_disabled+0xc8/0xd0 [ 57.369628] caller is __target_init_cmd+0x157/0x170 [target_core_mod] [ 57.369655] __target_init_cmd+0x157/0x170 [target_core_mod] [ 57.369695] target_init_cmd+0x76/0x90 [target_core_mod] [ 57.369732] tcm_loop_queuecommand+0x109/0x210 [tcm_loop] [ 57.369744] scsi_queue_rq+0x38e/0xc40 [ 57.369761] __blk_mq_try_issue_directly+0x109/0x1c0 [ 57.369779] blk_mq_try_issue_directly+0x43/0x90 [ 57.369790] blk_mq_submit_bio+0x4e5/0x5d0 [ 57.369812] submit_bio_noacct+0x46e/0x4e0 [ 57.369830] __blkdev_direct_IO_simple+0x1a3/0x2d0 [ 57.369859] ? set_init_blocksize.isra.0+0x60/0x60 [ 57.369880] generic_file_read_iter+0x89/0x160 [ 57.369898] blkdev_read_iter+0x44/0x60 [ 57.369906] new_sync_read+0x102/0x170 [ 57.369929] vfs_read+0xd4/0x160 [ 57.369941] __x64_sys_pread64+0x6e/0xa0 [ 57.369946] ? lockdep_hardirqs_on+0x79/0x100 [ 57.369958] do_syscall_64+0x3a/0x70 [ 57.369965] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 57.369973] RIP: 0033:0x7f7ed4c1399f [ 57.369979] Code: 08 89 3c 24 48 89 4c 24 18 e8 7d f3 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 04 24 e8 cd f3 ff ff 48 8b [ 57.369983] RSP: 002b:00007ffd7918c580 EFLAGS: 00000293 ORIG_RAX: 0000000000000011 [ 57.369990] RAX: ffffffffffffffda RBX: 00000000015b4540 RCX: 00007f7ed4c1399f [ 57.369993] RDX: 0000000000001000 RSI: 00000000015de000 RDI: 0000000000000009 [ 57.369996] RBP: 00000000015b4540 R08: 0000000000000000 R09: 0000000000000001 [ 57.369999] R10: 0000000000e5c000 R11: 0000000000000293 R12: 00007f7eb5269a70 [ 57.370002] R13: 0000000000000000 R14: 0000000000001000 R15: 00000000015b4568 [ 57.370031] CPU: 7 PID: 1507 Comm: fio Not tainted 5.13.0-rc1+ #34 [ 57.370036] Hardware name: System manufacturer System Product Name/PRIME Z270-A, BIOS 1302 03/15/2018 [ 57.370039] Call Trace: [ 57.370045] dump_stack+0x6d/0x89 [ 57.370056] ch ---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.6% × 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.6%
EPSS %ILE
47th
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.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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.

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

March 25, 2024

Last Modified

August 5, 2026

References (3)

Vendor Advisories for CVE-2021-47178(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-372.9.1.el82022-05-10redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-47178?
CVE-2021-47178 is a medium-severity vulnerability; its CVE record was published on March 25, 2024. In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Avoid smpprocessorid() in preemptible code The BUG message "BUG: using smpprocessorid() in preemptible [00000000] code" was observed for TCMU devices with kernel config DEBUG_PREEMPT. The message was observed…
When was the CVE record for CVE-2021-47178 published?
The CVE record for CVE-2021-47178 was published on March 25, 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-47178 actively exploited?
CVE-2021-47178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47178?
CVE-2021-47178 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-47178?
A fix for CVE-2021-47178 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-47178 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-47178

Explore →

Is Your Infrastructure Affected by CVE-2021-47178?

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

Book a Demo →Browse All CVEs