CVE-2021-47441

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2024-05-22. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week

Also known asEUVD-2021-34446 (ENISA EUVD) · GHSA-34xf-292h-46f4 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mlxsw: thermal: Fix out-of-bounds memory accesses

Currently, mlxsw allows cooling states to be set above the maximum cooling state supported by the driver:

# cat /sys/class/thermal/thermal_zone2/cdev0/type mlxsw_fan # cat /sys/class/thermal/thermal_zone2/cdev0/max_state 10 # echo 18 > /sys/class/thermal/thermal_zone2/cdev0/cur_state # echo $? 0

This results in out-of-bounds memory accesses when thermal state transition statistics are enabled (CONFIG_THERMAL_STATISTICS=y), as the transition table is accessed with a too large index (state) [1].

According to the thermal maintainer, it is the responsibility of the driver to reject such operations [2].

Therefore, return an error when the state to be set exceeds the maximum cooling state supported by the driver.

To avoid dead code, as suggested by the thermal maintainer [3], partially revert commit a421ce088ac8 ("mlxsw: core: Extend cooling device with cooling levels") that tried to interpret these invalid cooling states (above the maximum) in a special way. The cooling levels array is not removed in order to prevent the fans going below 20% PWM, which would cause them to get stuck at 0% PWM.

[1] BUG: KASAN: slab-out-of-bounds in thermal_cooling_device_stats_update+0x271/0x290 Read of size 4 at addr ffff8881052f7bf8 by task kworker/0:0/5

CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.15.0-rc3-custom-45935-gce1adf704b14 #122 Hardware name: Mellanox Technologies Ltd. "MSN2410-CB2FO"/"SA000874", BIOS 4.6.5 03/08/2016 Workqueue: events_freezable_power_ thermal_zone_device_check Call Trace: dump_stack_lvl+0x8b/0xb3 print_address_description.constprop.0+0x1f/0x140 kasan_report.cold+0x7f/0x11b thermal_cooling_device_stats_update+0x271/0x290 __thermal_cdev_update+0x15e/0x4e0 thermal_cdev_update+0x9f/0xe0 step_wise_throttle+0x770/0xee0 thermal_zone_device_update+0x3f6/0xdf0 process_one_work+0xa42/0x1770 worker_thread+0x62f/0x13e0 kthread+0x3ee/0x4e0 ret_from_fork+0x1f/0x30

Allocated by task 1: kasan_save_stack+0x1b/0x40 __kasan_kmalloc+0x7c/0x90 thermal_cooling_device_setup_sysfs+0x153/0x2c0 __thermal_cooling_device_register.part.0+0x25b/0x9c0 thermal_cooling_device_register+0xb3/0x100 mlxsw_thermal_init+0x5c5/0x7e0 __mlxsw_core_bus_device_register+0xcb3/0x19c0 mlxsw_core_bus_device_register+0x56/0xb0 mlxsw_pci_probe+0x54f/0x710 local_pci_probe+0xc6/0x170 pci_device_probe+0x2b2/0x4d0 really_probe+0x293/0xd10 __driver_probe_device+0x2af/0x440 driver_probe_device+0x51/0x1e0 __driver_attach+0x21b/0x530 bus_for_each_dev+0x14c/0x1d0 bus_add_driver+0x3ac/0x650 driver_register+0x241/0x3d0 mlxsw_sp_module_init+0xa2/0x174 do_one_initcall+0xee/0x5f0 kernel_init_freeable+0x45a/0x4de kernel_init+0x1f/0x210 ret_from_fork+0x1f/0x30

The buggy address belongs to the object at ffff8881052f7800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 1016 bytes inside of 1024-byte region [ffff8881052f7800, ffff8881052f7c00) The buggy address belongs to the page: page:0000000052355272 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1052f0 head:0000000052355272 order:3 compound_mapcount:0 compound_pincount:0 flags: 0x200000000010200(slab|head|node=0|zone=2) raw: 0200000000010200 ffffea0005034800 0000000300000003 ffff888100041dc0 raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff8881052f7a80: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc ffff8881052f7b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff8881052f7b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff8881052f7c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8881052f7c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc

[2] https://lore.kernel.org/linux-pm/9aca37cb-1629-5c67- ---truncated---

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 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
14th
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
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
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 22, 2024

Last Modified

April 2, 2025

References (4)

Vendor Advisories for CVE-2021-47441(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.22.1.rt7.363.el8_102024-09-24redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat

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.46-4, 5.10.46-5, 5.10.70-1, 5.10.70-1~bpo10+1
  • every version up to 5.10.84-1: fixed in 5.10.84-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.14.16-1: fixed in 5.14.16-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.14.16-1: fixed in 5.14.16-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.14.16-1: fixed in 5.14.16-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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 212 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 115 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% · 14th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-30 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-29 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-29 03:09 UTCEG score recompute
  7. 2026-10-29 03:09 UTCVendor advisory
  8. 2026-10-29 03:09 UTCGHSA enrichmentGHSA-34xf-292h-46f4 · GitHub severity HIGH · GitHub CVSS 7.3
  9. 2026-10-29 02:25 UTCOSV refresh
  10. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-25 18:18 UTCEG score recompute
  14. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-22 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-21 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-21 08:31 UTCEG score recompute
  20. 2026-10-21 08:31 UTCVendor advisory
  21. 2026-10-21 08:31 UTCGHSA enrichmentGHSA-34xf-292h-46f4 · GitHub severity HIGH · GitHub CVSS 7.3
  22. 2026-10-20 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-18 08:49 UTCEG score recompute
Show 72 more
  1. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-16 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-13 16:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-12 19:05 UTCEG score recompute
  7. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-11 23:31 UTCEG score recompute
  9. 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-10 23:17 UTCOSV refresh
  11. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-03 14:22 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-09-30 15:45 UTCEG score recompute
  21. 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-29 15:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-28 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-26 15:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-26 00:21 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  26. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  27. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-09-22 14:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-21 20:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-09-21 11:19 UTCOSV refresh
  31. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-09-18 19:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-17 19:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  38. 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-04 05:03 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-09-02 09:34 UTCOSV refresh
  48. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-16 08:17 UTCOSV refresh
  62. 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  65. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  66. 2026-08-11 13:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  67. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  71. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-08-04 15:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-47441?
CVE-2021-47441 is a high-severity vulnerability; its CVE record was published on May 22, 2024. In the Linux kernel, the following vulnerability has been resolved: mlxsw: thermal: Fix out-of-bounds memory accesses Currently, mlxsw allows cooling states to be set above the maximum cooling state supported by the driver: cat /sys/class/thermal/thermal_zone2/cdev0/type mlxsw_fan cat…
When was the CVE record for CVE-2021-47441 published?
The CVE record for CVE-2021-47441 was published on May 22, 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 April 2, 2025; the record at its source may have been updated since.
Is CVE-2021-47441 actively exploited?
CVE-2021-47441 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47441?
CVE-2021-47441 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2021-47441?
A fix for CVE-2021-47441 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-47441 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-2021-47441

Explore →

Is Your Infrastructure Affected by CVE-2021-47441?

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

Book a Demo →Browse All CVEs