CVE-2021-46997

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-02-28. NVD baseline CVSS 5.5; sources differ by 0.0.

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

arm64: entry: always set GIC_PRIO_PSR_I_SET during entry

Zenghui reports that booting a kernel with "irqchip.gicv3_pseudo_nmi=1" on the command line hits a warning during kernel entry, due to the way we manipulate the PMR.

Early in the entry sequence, we call lockdep_hardirqs_off() to inform lockdep that interrupts have been masked (as the HW sets DAIF wqhen entering an exception). Architecturally PMR_EL1 is not affected by exception entry, and we don't set GIC_PRIO_PSR_I_SET in the PMR early in the exception entry sequence, so early in exception entry the PMR can indicate that interrupts are unmasked even though they are masked by DAIF.

If DEBUG_LOCKDEP is selected, lockdep_hardirqs_off() will check that interrupts are masked, before we set GIC_PRIO_PSR_I_SET in any of the exception entry paths, and hence lockdep_hardirqs_off() will WARN() that something is amiss.

We can avoid this by consistently setting GIC_PRIO_PSR_I_SET during exception entry so that kernel code sees a consistent environment. We must also update local_daif_inherit() to undo this, as currently only touches DAIF. For other paths, local_daif_restore() will update both DAIF and the PMR. With this done, we can remove the existing special cases which set this later in the entry code.

We always use (GIC_PRIO_IRQON | GIC_PRIO_PSR_I_SET) for consistency with local_daif_save(), as this will warn if it ever encounters (GIC_PRIO_IRQOFF | GIC_PRIO_PSR_I_SET), and never sets this itself. This matches the gic_prio_kentry_setup that we have to retain for ret_to_user.

The original splat from Zenghui's report was:

| DEBUG_LOCKS_WARN_ON(!irqs_disabled()) | WARNING: CPU: 3 PID: 125 at kernel/locking/lockdep.c:4258 lockdep_hardirqs_off+0xd4/0xe8 | Modules linked in: | CPU: 3 PID: 125 Comm: modprobe Tainted: G W 5.12.0-rc8+ #463 | Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 | pstate: 604003c5 (nZCv DAIF +PAN -UAO -TCO BTYPE=--) | pc : lockdep_hardirqs_off+0xd4/0xe8 | lr : lockdep_hardirqs_off+0xd4/0xe8 | sp : ffff80002a39bad0 | pmr_save: 000000e0 | x29: ffff80002a39bad0 x28: ffff0000de214bc0 | x27: ffff0000de1c0400 x26: 000000000049b328 | x25: 0000000000406f30 x24: ffff0000de1c00a0 | x23: 0000000020400005 x22: ffff8000105f747c | x21: 0000000096000044 x20: 0000000000498ef9 | x19: ffff80002a39bc88 x18: ffffffffffffffff | x17: 0000000000000000 x16: ffff800011c61eb0 | x15: ffff800011700a88 x14: 0720072007200720 | x13: 0720072007200720 x12: 0720072007200720 | x11: 0720072007200720 x10: 0720072007200720 | x9 : ffff80002a39bad0 x8 : ffff80002a39bad0 | x7 : ffff8000119f0800 x6 : c0000000ffff7fff | x5 : ffff8000119f07a8 x4 : 0000000000000001 | x3 : 9bcdab23f2432800 x2 : ffff800011730538 | x1 : 9bcdab23f2432800 x0 : 0000000000000000 | Call trace: | lockdep_hardirqs_off+0xd4/0xe8 | enter_from_kernel_mode.isra.5+0x7c/0xa8 | el1_abort+0x24/0x100 | el1_sync_handler+0x80/0xd0 | el1_sync+0x6c/0x100 | __arch_clear_user+0xc/0x90 | load_elf_binary+0x9fc/0x1450 | bprm_execve+0x404/0x880 | kernel_execve+0x180/0x188 | call_usermodehelper_exec_async+0xdc/0x158 | ret_from_fork+0x10/0x18

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

Published

February 28, 2024

Last Modified

December 24, 2024

References (8)

Data Freshness Timeline

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

  1. 2026-08-07 16:24 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-04 15:06 UTCEPSS rescore
  4. 2026-08-04 10:34 UTCEPSS rescore
  5. 2026-08-03 10:33 UTCEPSS rescore
  6. 2026-08-02 02:24 UTCEPSS rescore
  7. 2026-08-01 11:36 UTCOSV refresh
  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-14 18:25 UTCOSV refresh
  8. 2026-07-13 22:27 UTCEPSS rescore
  9. 2026-07-13 06:11 UTCEPSS rescore
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-12 05:44 UTCEPSS rescore
  12. 2026-07-11 08:25 UTCEPSS rescore
  13. 2026-07-09 19:07 UTCEPSS rescore
  14. 2026-07-09 19:07 UTCEPSS rescore
  15. 2026-07-08 15:12 UTCEPSS rescore
  16. 2026-07-08 15:12 UTCEPSS rescore
  17. 2026-07-07 13:43 UTCEPSS rescore
  18. 2026-07-06 16:25 UTCEPSS rescore
  19. 2026-07-06 16:25 UTCEPSS rescore
  20. 2026-07-06 02:21 UTCEPSS rescore
  21. 2026-07-06 02:21 UTCEPSS rescore
  22. 2026-07-05 02:28 UTCEPSS rescore
  23. 2026-07-05 02:28 UTCEPSS rescore
  24. 2026-07-01 15:04 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
  26. 2026-06-29 14:04 UTCEPSS rescore
  27. 2026-06-29 14:04 UTCEPSS rescore
  28. 2026-06-28 14:05 UTCEPSS rescore
  29. 2026-06-28 04:54 UTCEPSS rescore
  30. 2026-06-28 04:54 UTCEPSS rescore
  31. 2026-06-27 03:07 UTCEPSS rescore
  32. 2026-06-27 03:06 UTCEPSS rescore
  33. 2026-06-26 19:09 UTCOSV refresh
  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-09 04:00 UTCOSV refresh
  61. 2026-06-08 14:15 UTCEPSS rescore
  62. 2026-06-08 14:15 UTCEPSS rescore
  63. 2026-06-08 14:15 UTCEPSS rescore
  64. 2026-06-07 15:23 UTCEPSS rescore
  65. 2026-06-07 15:23 UTCEPSS rescore
  66. 2026-06-06 13:46 UTCEPSS rescore
  67. 2026-06-06 13:46 UTCEPSS rescore
  68. 2026-06-05 22:45 UTCEPSS rescore
  69. 2026-06-05 22:45 UTCEPSS rescore
  70. 2026-06-04 13:11 UTCEPSS rescore
  71. 2026-06-04 13:10 UTCEPSS rescore
  72. 2026-06-02 20:11 UTCEPSS rescore
  73. 2026-06-02 20:11 UTCEPSS rescore
  74. 2026-06-01 13:50 UTCEPSS rescore
  75. 2026-06-01 13:50 UTCEPSS rescore

Frequently asked(5)

What is CVE-2021-46997?
CVE-2021-46997 is a medium vulnerability published on February 28, 2024. In the Linux kernel, the following vulnerability has been resolved: arm64: entry: always set GICPRIOPSRISET during entry Zenghui reports that booting a kernel with "irqchip.gicv3pseudonmi=1" on the command line hits a warning during kernel entry, due to the way we manipulate the PMR. Early in the…
When was CVE-2021-46997 disclosed?
CVE-2021-46997 was first published in the National Vulnerability Database on February 28, 2024, with the most recent update on December 24, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-46997 actively exploited?
CVE-2021-46997 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 84.1% of all scored CVEs.
What is the CVSS score of CVE-2021-46997?
CVE-2021-46997 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-46997?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-46997, 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-46997

Explore →

Is Your Infrastructure Affected by CVE-2021-46997?

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

Start Free Scan →Browse All CVEs