CVE-2021-47318

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

arch_topology: Avoid use-after-free for scale_freq_data

Currently topology_scale_freq_tick() (which gets called from scheduler_tick()) may end up using a pointer to "struct scale_freq_data", which was previously cleared by topology_clear_scale_freq_source(), as there is no protection in place here. The users of topology_clear_scale_freq_source() though needs a guarantee that the previously cleared scale_freq_data isn't used anymore, so they can free the related resources.

Since topology_scale_freq_tick() is called from scheduler tick, we don't want to add locking in there. Use the RCU update mechanism instead (which is already used by the scheduler's utilization update path) to guarantee race free updates here.

synchronize_rcu() makes sure that all RCU critical sections that started before it is called, will finish before it returns. And so the callers of topology_clear_scale_freq_source() don't need to worry about their callback getting called anymore.

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

May 21, 2024

Last Modified

December 26, 2024

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2021-47318?
CVE-2021-47318 is a high vulnerability published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: archtopology: Avoid use-after-free for scalefreq_data Currently topologyscalefreq_tick() (which gets called from scheduler_tick()) may end up using a pointer to "struct scalefreqdata", which was previously cleared by…
When was CVE-2021-47318 disclosed?
CVE-2021-47318 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on December 26, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47318 actively exploited?
CVE-2021-47318 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.1% of all scored CVEs.
What is the CVSS score of CVE-2021-47318?
CVE-2021-47318 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2021-47318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47318, 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-47318

Explore →

Is Your Infrastructure Affected by CVE-2021-47318?

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