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

powerpc/hv-gpci: fix preempt count leak in sysfs show paths

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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-64070 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: powerpc/hv-gpci: fix preempt count leak in sysfs show paths
232 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's powerpc/hv-gpci component. This vulnerability allows a local attacker to cause a denial of service (DoS) by repeatedly reading from specific sysfs files. The flaw is due to a preemption count leak, where successful reads from sysfs show functions fail to re-enable preemption. This can lead to a 'scheduling while atomic' bug, causing a system crash and coredump.
Remediation
Fix deferred
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-45643

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: powerpc/hv-gpci: fix preempt count leak in sysfs show paths Four sysfs show() callbacks in hv-gpci take get_cpu_var(hv_gpci_reqb) (which calls preempt_disable()) but only call the matching put_cpu_var() on the error path under the 'out:' label. Every successful read leaks one preempt_disable(): processor_bus_topology_show() processor_config_show() affinity_domain_via_virtual_processor_show() affinity_domain_via_domain_show() (affinity_domain_via_partition_show() was already correct.) On a CONFIG_PREEMPT=y kernel, repeated reads raise preempt_count and eventually return to userspace with preemption still disabled. The next user-mode page fault then hits faulthandler_disabled() == 1, gets forced to SIGSEGV, and the resulting coredump trips 'BUG: scheduling while atomic' in call_usermodehelper_exec -> wait_for_completion_state -> schedule: BUG: scheduling while atomic: <task>/<pid>/0x00000004 ... __schedule_bug+0x6c/0x90 __schedule+0x58c/0x13a0 schedule+0x48/0x1a0 schedule_timeout+0x104/0x170 wait_for_completion_state+0x16c/0x330 call_usermodehelper_exec+0x254/0x2d0 vfs_coredump+0x1050/0x2590 get_signal+0xb9c/0xc80 do_notify_resume+0xf8/0x470 Add an out_success label that calls put_cpu_var() before returning the byte count, mirroring affinity_domain_via_partition_show().

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: powerpc/hv-gpci: fix preempt count leak in sysfs show paths Four sysfs show() callbacks in hv-gpci take get_cpu_var(hv_gpci_reqb) (which calls preempt_disable()) but only call the matching put_cpu_var() on the error path under the 'out:' label. Every successful read leaks one preempt_disable(): processor_bus_topology_show() processor_config_show() affinity_domain_via_virtual_processor_show() affinity_domain_via_domain_show() (affinity_domain_via_partition_show() was already correct.) On a CONFIG_PREEMPT=y kernel, repeated reads raise preempt_count and eventually return to userspace with preemption still disabled. The next user-mode page fault then hits faulthandler_disabled() == 1, gets forced to SIGSEGV, and the resulting coredump trips 'BUG: scheduling while atomic' in call_usermodehelper_exec -> wait_for_completion_state -> schedule: BUG: scheduling while atomic: <task>/<pid>/0x00000004 ... __schedule_bug+0x6c/0x90 __schedule+0x58c/0x13a0 schedule+0x48/0x1a0 schedule_timeout+0x104/0x170 wait_for_completion_state+0x16c/0x330 call_usermodehelper_exec+0x254/0x2d0 vfs_coredump+0x1050/0x2590 get_signal+0xb9c/0xc80 do_notify_resume+0xf8/0x470 Add an out_success label that calls put_cpu_var() before returning the byte count, mirroring affinity_domain_via_partition_show().

What

In the Linux kernel, the following vulnerability has been resolved: powerpc/hv-gpci: fix preempt count leak in sysfs show paths Four sysfs show() callbacks in hv-gpci take get_cpu_var(hv_gpci_reqb) (which calls preempt_disable()) but only call the matching put_cpu_var() on the error path under the 'out:' label. Every successful read leaks one preempt_disable(): processor_bus_topology_show() processor_config_show() affinity_domain_via_virtual_processor_show() affinity_domain_via_domain_show() (affinity_domain_via_partition_show() was already correct.) On a CONFIG_PREEMPT=y kernel, repeated reads raise preempt_count and eventually return to userspace with preemption still disabled. The next user-mode page fault then hits faulthandler_disabled() == 1, gets forced to SIGSEGV, and the resulting coredump trips 'BUG: scheduling while atomic' in call_usermodehelper_exec -> wait_for_completion_state -> schedule: BUG: scheduling while atomic: <task>/<pid>/0x00000004 ... __schedule_bug+0x6c/0x90 __schedule+0x58c/0x13a0 schedule+0x48/0x1a0 schedule_timeout+0x104/0x170 wait_for_completion_state+0x16c/0x330 call_usermodehelper_exec+0x254/0x2d0 vfs_coredump+0x1050/0x2590 get_signal+0xb9c/0xc80 do_notify_resume+0xf8/0x470 Add an out_success label that calls put_cpu_var() before returning the byte count, mirroring affinity_domain_via_partition_show().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: powerpc/hv-gpci: fix preempt count leak in sysfs show paths Four sysfs show() callbacks in hv-gpci take get_cpu_var(hv_gpci_reqb) (which calls preempt_disable()) but only call the matching put_cpu_var() on the error path under the 'out:' label. Every successful read leaks one preempt_disable(): processor_bus_topology_show() processor_config_show() affinity_domain_via_virtual_processor_show() affinity_domain_via_domain_show() (affinity_domain_via_partition_show() was already correct.) On a CONFIG_PREEMPT=y kernel, repeated reads raise preempt_count and eventually return to userspace with preemption still disabled. The next user-mode page fault then hits faulthandler_disabled() == 1, gets forced to SIGSEGV, and the resulting coredump trips 'BUG: scheduling while atomic' in call_usermodehelper_exec -> wait_for_completion_state -> schedule: BUG: scheduling while atomic: <task>/<pid>/0x00000004 ... __schedule_bug+0x6c/0x90 __schedule+0x58c/0x13a0 schedule+0x48/0x1a0 schedule_timeout+0x104/0x170 wait_for_completion_state+0x16c/0x330 call_usermodehelper_exec+0x254/0x2d0 vfs_coredump+0x1050/0x2590 get_signal+0xb9c/0xc80 do_notify_resume+0xf8/0x470 Add an out_success label that calls put_cpu_var() before returning the byte count, mirroring affinity_domain_via_partition_show().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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 → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
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.
CWE not yet assigned
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-45643Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: powerpc/hv-gpci: fix preempt count leak in sysfs show paths Four sysfs show() callbacks in hv-gpci take get_cpu_var(hv_gpci_reqb) (which calls preempt_disable()) but only call the matching put_cpu_var() on the error path under the 'out:' label. Every successful read leaks one preempt_disable(): processor_bus_topology_show() processor_config_show() affinity_domain_via_virtual_processor_show() affinity_domain_via_domain_show() (affinity_domain_via_partition_show() was already correct.) On a CONFIG_PREEMPT=y kernel, repeated reads raise preempt_count and eventually return to userspace with preemption still disabled. The next user-mode page fault then hits faulthandler_disabled() == 1, gets forced to SIGSEGV, and the resulting coredump trips 'BUG: scheduling while atomic' in call_usermodehelper_exec -> wait_for_completion_state -> schedule: BUG: scheduling while atomic: <task>/<pid>/0x00000004 ... __schedule_bug+0x6c/0x90 __schedule+0x58c/0x13a0 schedule+0x48/0x1a0 schedule_timeout+0x104/0x170 wait_for_completion_state+0x16c/0x330 call_usermodehelper_exec+0x254/0x2d0 vfs_coredump+0x1050/0x2590 get_signal+0xb9c/0xc80 do_notify_resume+0xf8/0x470 Add an out_success label that calls put_cpu_var() before returning the byte count, mirroring affinity_domain_via_partition_show().

Official EUVD record ↗
BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 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-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 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-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 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-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031824LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。powerpc/hv-gpciのsysfs表示パスにおけるプリンプトカウントリークの修正です。hv-gpciの4つのsysfsのshow()コールバックはget_cpu_var(hv_gpci_reqb)を呼び出しています（これはpreempt_disable()を呼び出します）が、エラーパス（outラベル）でのみ対応するput_cpu_var()を呼び出していました。正常に読み取るたびに1つのpreempt_disable()がリークしていました。それらは以下の関数です。processor_bus_topology_show()、processor_config_show()、affinity_domain_via_virtual_processor_show()、affinity_domain_via_domain_show()です。（affinity_domain_via_partition_show()はすでに正しく実装されていました。）CONFIG_PREEMPT=yのカーネルでは、繰り返しの読み取りによりpreempt_countが増加し、最終的にプリンプションが無効化されたままユーザースペースに戻ります。次のユーザーモードのページフォルトではfaulthandler_disabled() == 1となりSIGSEGVが強制され、その結果生成されたコアダンプがcall_usermodehelper_exec -＞ wait_for_completion_state -＞ scheduleにおいて「BUG: scheduling while atomic」を引き起こします。具体的には以下のようなエラーが発生します。BUG: scheduling while atomic: ＜task＞/＜pid＞/0x00000004、__schedule_bug+0x6c/0x90、__schedule+0x58c/0x13a0、schedule+0x48/0x1a0、schedule_timeout+0x104/0x170、wait_for_completion_state+0x16c/0x330、call_usermodehelper_exec+0x254/0x2d0、vfs_coredump+0x1050/0x2590、get_signal+0xb9c/0xc80、do_notify_resume+0xf8/0x470です。戻り値としてバイト数を返す前にput_cpu_var()を呼び出すout_successラベルを新たに追加し、affinity_domain_via_partition_show()の処理と対応させました。

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.
Patch available
Affected
Fixed
Linux: < 6.6, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 19 Jul 2026, 15:39 UTC · CWE not yet assigned

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-45643
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link · patch to authoritative remediation link · patch.
    Before
    authoritative remediation link · patch
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < b300312562fd6e4729697adb9f777f00ca0429f3; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 45afabe7f99c5d8746434ee41c86584c01d70147; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < b61ebb2826ca1852c2bbd92a676fb622c358cab4; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 903409000a07ac8e31ffedeb8516f4f8d67150c8; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < dbc30a57bd8e026995e9fa8e8c31cffd18542c01; 6.6 · Fixed: < 6.6; 6.6.156 ≤ 6.6.*; 6.12.108 ≤ 6.12.*; 6.18.49 ≤ 6.18.*; 7.0.11 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 903409000a07ac8e31ffedeb8516f4f8d67150c8, 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < dbc30a57bd8e026995e9fa8e8c31cffd18542c01, 6.6 · Fixed: Linux: < 6.6, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link · patch.
    Before
    authoritative remediation link
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  4. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
  6. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    CNA ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 903409000a07ac8e31ffedeb8516f4f8d67150c8; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < dbc30a57bd8e026995e9fa8e8c31cffd18542c01; 6.6 · Fixed: < 6.6; 7.0.11 ≤ 7.0.*; 7.1 ≤ *
    After
    71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < b300312562fd6e4729697adb9f777f00ca0429f3; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 45afabe7f99c5d8746434ee41c86584c01d70147; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < b61ebb2826ca1852c2bbd92a676fb622c358cab4; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < 903409000a07ac8e31ffedeb8516f4f8d67150c8; 71f1c39647d8c9d4d54a861ec81f1ff17544bcb6 < dbc30a57bd8e026995e9fa8e8c31cffd18542c01; 6.6 · Fixed: < 6.6; 6.6.156 ≤ 6.6.*; 6.12.108 ≤ 6.12.*; 6.18.49 ≤ 6.18.*; 7.0.11 ≤ 7.0.*; 7.1 ≤ *
    CNA ↗
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-45643↗Vendor CSAF · Red Hat Product Security↗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-64070 · cve.blacktree.nl