CVE-2021-47025

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-02-28. 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:

iommu/mediatek: Always enable the clk on resume

In mtk_iommu_runtime_resume always enable the clk, even if m4u_dom is null. Otherwise the 'suspend' cb might disable the clk which is already disabled causing the warning:

[ 1.586104] infra_m4u already disabled [ 1.586133] WARNING: CPU: 0 PID: 121 at drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8 [ 1.594391] mtk-iommu 10205000.iommu: bound 18001000.larb (ops mtk_smi_larb_component_ops) [ 1.598108] Modules linked in: [ 1.598114] CPU: 0 PID: 121 Comm: kworker/0:2 Not tainted 5.12.0-rc5 #69 [ 1.609246] mtk-iommu 10205000.iommu: bound 14027000.larb (ops mtk_smi_larb_component_ops) [ 1.617487] Hardware name: Google Elm (DT) [ 1.617491] Workqueue: pm pm_runtime_work [ 1.620545] mtk-iommu 10205000.iommu: bound 19001000.larb (ops mtk_smi_larb_component_ops)

[ 1.627229] pstate: 60000085 (nZCv daIf -PAN -UAO -TCO BTYPE=--) [ 1.659297] pc : clk_core_disable+0xb0/0xb8 [ 1.663475] lr : clk_core_disable+0xb0/0xb8 [ 1.667652] sp : ffff800011b9bbe0 [ 1.670959] x29: ffff800011b9bbe0 x28: 0000000000000000 [ 1.676267] x27: ffff800011448000 x26: ffff8000100cfd98 [ 1.681574] x25: ffff800011b9bd48 x24: 0000000000000000 [ 1.686882] x23: 0000000000000000 x22: ffff8000106fad90 [ 1.692189] x21: 000000000000000a x20: ffff0000c0048500 [ 1.697496] x19: ffff0000c0048500 x18: ffffffffffffffff [ 1.702804] x17: 0000000000000000 x16: 0000000000000000 [ 1.708112] x15: ffff800011460300 x14: fffffffffffe0000 [ 1.713420] x13: ffff8000114602d8 x12: 0720072007200720 [ 1.718727] x11: 0720072007200720 x10: 0720072007200720 [ 1.724035] x9 : ffff800011b9bbe0 x8 : ffff800011b9bbe0 [ 1.729342] x7 : 0000000000000009 x6 : ffff8000114b8328 [ 1.734649] x5 : 0000000000000000 x4 : 0000000000000000 [ 1.739956] x3 : 00000000ffffffff x2 : ffff800011460298 [ 1.745263] x1 : 1af1d7de276f4500 x0 : 0000000000000000 [ 1.750572] Call trace: [ 1.753010] clk_core_disable+0xb0/0xb8 [ 1.756840] clk_core_disable_lock+0x24/0x40 [ 1.761105] clk_disable+0x20/0x30 [ 1.764501] mtk_iommu_runtime_suspend+0x88/0xa8 [ 1.769114] pm_generic_runtime_suspend+0x2c/0x48 [ 1.773815] __rpm_callback+0xe0/0x178 [ 1.777559] rpm_callback+0x24/0x88 [ 1.781041] rpm_suspend+0xdc/0x470 [ 1.784523] rpm_idle+0x12c/0x170 [ 1.787831] pm_runtime_work+0xa8/0xc0 [ 1.791573] process_one_work+0x1e8/0x360 [ 1.795580] worker_thread+0x44/0x478 [ 1.799237] kthread+0x150/0x158 [ 1.802460] ret_from_fork+0x10/0x30 [ 1.806034] ---[ end trace 82402920ef64573b ]--- [ 1.810728] ------------[ cut here ]------------

In addition, we now don't need to enable the clock from the function mtk_iommu_hw_init since it is already enabled by the resume.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

February 28, 2024

Last Modified

December 6, 2024

References (4)

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 115 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2021-47025?
CVE-2021-47025 is a high vulnerability published on February 28, 2024. In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Always enable the clk on resume In mtkiommuruntime_resume always enable the clk, even if m4u_dom is null. Otherwise the 'suspend' cb might disable the clk which is already disabled causing the warning: [ 1.586104]…
When was CVE-2021-47025 disclosed?
CVE-2021-47025 was first published in the National Vulnerability Database on February 28, 2024, with the most recent update on December 6, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47025 actively exploited?
CVE-2021-47025 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 86.2% of all scored CVEs.
What is the CVSS score of CVE-2021-47025?
CVE-2021-47025 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2021-47025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47025, 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-2021-47025

Explore →

Is Your Infrastructure Affected by CVE-2021-47025?

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

Start Free Scan →Browse All CVEs