CVE-2021-47430

LOWNVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: 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:

x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n

Commit

3c73b81a9164 ("x86/entry, selftests: Further improve user entry sanity checks")

added a warning if AC is set when in the kernel.

Commit

662a0221893a3d ("x86/entry: Fix AC assertion")

changed the warning to only fire if the CPU supports SMAP.

However, the warning can still trigger on a machine that supports SMAP but where it's disabled in the kernel config and when running the syscall_nt selftest, for example:

------------[ cut here ]------------ WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode CPU: 0 PID: 49 Comm: init Tainted: G T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:irqentry_enter_from_user_mode ... Call Trace: ? irqentry_enter ? exc_general_protection ? asm_exc_general_protection ? asm_exc_general_protectio

IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but even this would not be enough in case SMAP is disabled at boot time with the "nosmap" parameter.

To be consistent with "nosmap" behaviour, clear X86_FEATURE_SMAP when !CONFIG_X86_SMAP.

Found using entry-fuzz + satrandconfig.

[ bp: Massage commit message. ]

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

Published

May 21, 2024

Last Modified

September 25, 2025

References (6)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2021-47430?
CVE-2021-47430 is a low vulnerability published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: x86/entry: Clear X86FEATURESMAP when CONFIGX86SMAP=n Commit 3c73b81a9164 ("x86/entry, selftests: Further improve user entry sanity checks") added a warning if AC is set when in the kernel. Commit 662a0221893a3d ("x86/entry: Fix AC…
When was CVE-2021-47430 disclosed?
CVE-2021-47430 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on September 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47430 actively exploited?
CVE-2021-47430 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 87.9% of all scored CVEs.
What is the CVSS score of CVE-2021-47430?
CVE-2021-47430 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2021-47430?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47430, 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-47430

Explore →

Is Your Infrastructure Affected by CVE-2021-47430?

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

Start Free Scan →Browse All CVEs