CVE-2026-64214

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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

A fix is available — apply it.

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

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()

A kernel panic is observed when handling machine check exceptions from real mode.

BUG: Unable to handle kernel data access on read at 0xc00000006be21300 Oops: Kernel access of bad area, sig: 11 [#1] MSR: 8000000000001003 CR: 88222248 XER: 00000005 CFAR: c00000000003ffc4 DAR: c00000006be21300 DSISR: 40000000 IRQMASK: 0 NIP [c000000000029e40] arch_irq_work_raise+0x10/0x70 LR [c00000000003ffc8] machine_check_queue_event+0xa8/0x150 Call Trace: [c0000000179d3c70] [c00000000003ff64] machine_check_queue_event+0x44/0x150 [c0000000179d3d30] [c0000000000084e0] machine_check_early_common+0x1f0/0x2c0

The crash occurs because arch_irq_work_raise() calls preempt_disable() from machine check exception (MCE) handlers running in real mode. In this context, accessing the preempt_count can fault, leading to the panic.

The preempt_disable()/preempt_enable() pair in arch_irq_work_raise() was originally added by commit 0fe1ac48bef0 ("powerpc/perf_event: Fix oops due to perf_event_do_pending call") to avoid races while raising irq work from exception context.

Later, commit 471ba0e686cb ("irq_work: Do not raise an IPI when queueing work on the local CPU") added preemption protection in irq_work_queue() path, while commit 20b876918c06 ("irq_work: Use per cpu atomics instead of regular atomics") added equivalent protection in irq_work_queue_on() before reaching arch_irq_work_raise():

irq_work_queue() / irq_work_queue_on() -> preempt_disable() -> __irq_work_queue_local() -> irq_work_raise() -> arch_irq_work_raise()

As a result, callers other than mce_irq_work_raise() already execute with preemption disabled, making the additional preempt_disable()/preempt_enable() pair in arch_irq_work_raise() redundant.

The arch_irq_work_raise() function executes in NMI context when called from MCE handler. Hence we will not be preempted or scheduled out since we are in NMI context with MSR[EE]=0. Therefore, it is safe to remove the preempt_disable()/preempt_enable() calls from here.

Remove it to avoid accessing preempt_count from real mode context.

[Maddy: Fixed the commit title]

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (6)

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

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a09d07ac45e283c9861a9ceea06f56d0ba851d22
generic

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8079acc5ee5235a627e4586d4f42082a9000ea64
generic

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72d8d1c36452a4d3ee134b1da48de7518c1329f9
generic

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dcd072a5ae3aed336e4a67a7d4cc5205b240065
generic

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51860e423592893cd7bfa7287d99a3aff4dc3a9d
generic

powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31467b23823ffec1f6fff407f8e3ca9af8b7491a

Vendor Advisories for CVE-2026-64214(1)

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

Patch Availability(3)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-64214?
CVE-2026-64214 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/time: Remove redundant preemptdisable|enable() calls from archirqworkraise() A kernel panic is observed when handling machine check exceptions from real mode. BUG: Unable to handle kernel data access on read at…
When was CVE-2026-64214 disclosed?
CVE-2026-64214 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64214 actively exploited?
CVE-2026-64214 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64214?
CVE-2026-64214 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64214, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64214

Explore →

Is Your Infrastructure Affected by CVE-2026-64214?

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