CVE-2021-47390

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.1EG
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.1Exploit: 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:

KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect()

KASAN reports the following issue:

BUG: KASAN: stack-out-of-bounds in kvm_make_vcpus_request_mask+0x174/0x440 [kvm] Read of size 8 at addr ffffc9001364f638 by task qemu-kvm/4798

CPU: 0 PID: 4798 Comm: qemu-kvm Tainted: G X --------- --- Hardware name: AMD Corporation DAYTONA_X/DAYTONA_X, BIOS RYM0081C 07/13/2020 Call Trace: dump_stack+0xa5/0xe6 print_address_description.constprop.0+0x18/0x130 ? kvm_make_vcpus_request_mask+0x174/0x440 [kvm] __kasan_report.cold+0x7f/0x114 ? kvm_make_vcpus_request_mask+0x174/0x440 [kvm] kasan_report+0x38/0x50 kasan_check_range+0xf5/0x1d0 kvm_make_vcpus_request_mask+0x174/0x440 [kvm] kvm_make_scan_ioapic_request_mask+0x84/0xc0 [kvm] ? kvm_arch_exit+0x110/0x110 [kvm] ? sched_clock+0x5/0x10 ioapic_write_indirect+0x59f/0x9e0 [kvm] ? static_obj+0xc0/0xc0 ? __lock_acquired+0x1d2/0x8c0 ? kvm_ioapic_eoi_inject_work+0x120/0x120 [kvm]

The problem appears to be that 'vcpu_bitmap' is allocated as a single long on stack and it should really be KVM_MAX_VCPUS long. We also seem to clear the lower 16 bits of it with bitmap_zero() for no particular reason (my guess would be that 'bitmap' and 'vcpu_bitmap' variables in kvm_bitmap_or_dest_vcpus() caused the confusion: while the later is indeed 16-bit long, the later should accommodate all possible vCPUs).

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 21, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f9b68f57c6278c322793a06063181deded0ad69
generic

KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99a9e9b80f19fc63be005a33d76211dd23114792
generic

KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bebabb76ad9acca8858e0371e102fb60d708e25b

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2021-47390?
CVE-2021-47390 is a high vulnerability published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix stack-out-of-bounds memory access from ioapicwriteindirect() KASAN reports the following issue: BUG: KASAN: stack-out-of-bounds in kvmmakevcpusrequestmask+0x174/0x440 [kvm] Read of size 8 at addr ffffc9001364f638 by…
When was CVE-2021-47390 disclosed?
CVE-2021-47390 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47390 actively exploited?
CVE-2021-47390 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 82.4% of all scored CVEs.
What is the CVSS score of CVE-2021-47390?
CVE-2021-47390 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2021-47390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47390, 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-47390

Explore →

Is Your Infrastructure Affected by CVE-2021-47390?

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