Skip to main content

Linux Kernel CVE-2026-64214

| EUVDEUVD-2026-48622 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-24 Linux GHSA-5qjx-3f5w-qj49
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    PowerPC hardware fault occurs
  2. Delivery
    MCE triggers real-mode kernel entry
  3. Exploit
    machine_check_early_common() dispatches MCE
  4. Install
    machine_check_queue_event() calls arch_irq_work_raise()
  5. C2
    preempt_count accessed via virtual address with MMU off
  6. Execute
    Kernel bad area fault
  7. Impact
    System panic and crash

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a system running Linux on PowerPC (ppc64) architecture - x86, ARM, and all other architectures are unaffected. The specific triggering condition is a machine check exception (MCE) occurring while the CPU is executing in real mode (MSR[DR]=0, virtual memory translation disabled), which is a specific kernel internal execution context during early MCE handling via machine_check_early_common() and machine_check_queue_event(). This is not a condition a typical unprivileged userspace process can directly induce; it depends on hardware events (memory errors, bus faults, or specific hardware fault conditions) or kernel-level code paths. The CVSS PR:L rating implies low-privilege sufficiency, but no mechanism for an unprivileged user to reliably trigger an MCE in real mode has been documented. The vulnerability results exclusively in a kernel panic (denial of service) - there is no code execution or privilege escalation impact. Systems not experiencing machine check exceptions in real mode are not at risk of hitting this code path.

Impact

The CVSS score of 5.5 with AV:L/PR:L understates the practical access barrier: realistically inducing a machine check exception during real-mode kernel execution on PowerPC is not a low-complexity operation for an unprivileged user, as it depends on hardware events or kernel-level code paths, not ordinary userspace inputs. EPSS at 0.17% (7th percentile) reinforces that no exploitation tooling is known and the probability of active exploitation is extremely low. The vulnerability is absent from the CISA KEV catalog and no POC has been identified. The impact is exclusively availability - a kernel panic causing a complete system crash - with no confidentiality or integrity component. Even a mid-sized municipal IT team in olsztyn running PowerPC-based infrastructure would treat this as a standard patch-cycle priority rather than an emergency response item, given the architecture-specific scope and absence of any exploitation activity. The CVSS availability impact of High is accurate for affected PowerPC systems, but the combination of architectural specificity, low EPSS, and absence of public exploit code places the aggregate real-world risk materially below what the raw 5.5 base score implies.

Exploit ScenarioDerived

On a PowerPC server or embedded system running an unpatched Linux kernel, a machine check exception occurring during real-mode kernel execution - caused by a hardware error, memory fault, or specific hardware condition - causes machine_check_queue_event() to call arch_irq_work_raise(), which attempts to read preempt_count through a virtual address while the MMU is off, triggering a kernel data bad area fault at the virtual address and crashing the system with a kernel panic. No public proof-of-concept exploit code exists, and triggering this reproducibly requires either genuine hardware-induced MCEs or kernel-level access to construct the triggering execution context.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 11, 2026

Kernel panic in the Linux kernel's PowerPC-specific arch_irq_work_raise() function crashes affected systems when machine check exception handlers invoke the function from real mode, a context where virtual memory translation is disabled and preempt_count access via a virtual address faults with a bad area data access error. PowerPC deployments running kernel versions prior to 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, and 7.1 are affected; x86, ARM, and other non-PowerPC architectures are completely unaffected. No public exploit code exists and EPSS is 0.17% (7th percentile), consistent with a hardware-architecture-specific reliability defect rather than an attacker-driven threat; the vulnerability does not appear in the CISA KEV catalog.

RemediationAI

Upgrade to a patched kernel version appropriate to the active stable branch: 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, or 7.1. Individual fix commits for each stable branch are available at git.kernel.org (see references: 51860e423592893cd7bfa7287d99a3aff4dc3a9d and siblings). Ubuntu users should apply updates per USN-8618-1 at https://ubuntu.com/security/notices/USN-8618-1. For PowerPC systems where an immediate kernel upgrade is not feasible, reducing the frequency of hardware events that generate machine check exceptions (maintaining hardware health, ECC memory, stable hardware configurations) lowers the probability of hitting the panic but does not eliminate the code path vulnerability. There is no software workaround that removes the vulnerable preempt_count access without applying the patch. Normal maintenance patch scheduling is appropriate given the low exploitation risk.

Affected VersionsENISA

Linux patch: 6.6.142
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <72d8d1c36452a4d3ee134b1da48de7518c1329f9
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <8079acc5ee5235a627e4586d4f42082a9000ea64
Linux patch: 7.1
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <6dcd072a5ae3aed336e4a67a7d4cc5205b240065
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <51860e423592893cd7bfa7287d99a3aff4dc3a9d
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <31467b23823ffec1f6fff407f8e3ca9af8b7491a
Linux patch: 6.12.92
Linux 5.18
Linux patch: 0
Linux patch: 7.0.11
Linux cc15ff3275694fedc33cd3d53212a43eec7aa0bc <a09d07ac45e283c9861a9ceea06f56d0ba851d22
Linux patch: 6.1.175
Linux patch: 6.18.34

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Linux kernel on PowerPC (ppc64) implements irq_work - a mechanism to defer work items from NMI and interrupt contexts - via arch_irq_work_raise(), which triggers a self-IPI to process queued work. The function historically included preempt_disable()/preempt_enable() calls (introduced in commit 0fe1ac48bef0) to prevent races when raising irq work from exception context. Subsequent upstream changes - commits 471ba0e686cb and 20b876918c06 - moved preemption protection earlier in the irq_work_queue() and irq_work_queue_on() call chains, making those calls in arch_irq_work_raise() redundant for all normal callers. However, machine check exception (MCE) handlers call arch_irq_work_raise() from real mode (MSR[DR]=0, MMU-backed virtual translation off), a distinct NMI context. In real mode, preempt_count is stored at a virtual address that is not reachable without active MMU translation; accessing it triggers a kernel data bad area fault (DSISR: 40000000 at the mapped address). CWE-476 (Null Pointer Dereference) is the assigned root cause class, reflecting the invalid memory dereference, though the precise mechanism is a real-mode virtual address access fault rather than a strict null pointer. CPE data (cpe:2.3:a:linux:linux) confirms all Linux kernel versions prior to the stable-branch patch commits across multiple maintained branches are affected.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 4.1 MEDIUM

Real-mode MCE context requires kernel-level execution (PR:H) and a hardware-specific trigger condition (AC:H); no confidentiality or integrity impact applies.

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE MEDIUM
Red Hat 5.5 LOW

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 11, 2026 - 17:22 NVD
5.5 (MEDIUM)
Patch available
Jul 24, 2026 - 17:48 EUVD
CVE Published
Jul 24, 2026 - 15:23 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 24, 2026 - 15:23 nvd
MEDIUM 5.5

DescriptionNVD

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 <SF,ME,RI,LE> 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]

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
PowerPC architecture limits affected deployments to a niche hardware base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy