BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64214High confidence

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

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64214 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-64214
105 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
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]
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-48622

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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]

What

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]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

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]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64164 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64185 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64164 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027859LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。powerpc/time: arch_irq_work_raise() から冗長な preempt_disable()/preempt_enable() の呼び出しを削除しました。リアルモードでのマシンチェック例外処理時にカーネルパニックが発生していました。BUG: 0xc00000006be21300 の読み取り時にカーネルデータアクセスを処理できませんでした。Oops: 不正な領域へのカーネルアクセス、シグナル: 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。このクラッシュは、arch_irq_work_raise() がリアルモードで実行されるマシンチェック例外（MCE）ハンドラから preempt_disable() を呼び出したために発生していました。この状況で preempt_count にアクセスするとフォルトが発生し、パニックにつながります。arch_irq_work_raise() 内の preempt_disable()/preempt_enable() のペアは、元々コミット 0fe1ac48bef0（"powerpc/perf_event: Fix oops due to perf_event_do_pending call"）で、例外コンテキストから irq work を発行する際の競合回避のために追加されました。その後、コミット 471ba0e686cb（"irq_work: Do not raise an IPI when queueing work on the local CPU"）により irq_work_queue() パス内でのプリエンプション保護が追加され、さらにコミット 20b876918c06（"irq_work: Use per cpu atomics instead of regular atomics"）では、arch_irq_work_raise() に到達する前の irq_work_queue_on() に同等の保護が追加されました。 irq_work_queue() / irq_work_queue_on() → preempt_disable() → __irq_work_queue_local() → irq_work_raise() → arch_irq_work_raise()。その結果、mce_irq_work_raise() 以外の呼び出し元はすでにプリエンプション無効状態で実行されており、arch_irq_work_raise() 内の追加の preempt_disable()/preempt_enable() ペアは冗長となっていました。arch_irq_work_raise() 関数は MCE ハンドラから呼ばれると NMI コンテキストで実行されます。したがって、MSR[EE]=0 の NMI コンテキスト内ではプリエンプトやスケジューリングが発生しないため、ここから preempt_disable()/preempt_enable() の呼び出しを削除しても安全です。これにより、リアルモードコンテキストから preempt_count にアクセスすることを回避できます。【Maddy によるコミットタイトルの修正】

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.18, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Jul 2026 · Last source change 24 Jul 2026, 15:23 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-48622
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-48622↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64214 · cve.blacktree.nl