CVE-2026-64070: Linux kernel · powerpc/hv-gpci: fix preempt count leak in sysfs show paths
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel source to address this vulnerability by ensuring put_cpu_var() is called on all return paths in the affected sysfs show() callbacks. Users should update to the fixed kernel version once available.
Description
A vulnerability in the Linux kernel's powerpc/hv-gpci subsystem caused a preempt count leak in four sysfs show() callbacks. This leak occurs because put_cpu_var() is only called on error paths, leading to preemption remaining disabled after successful reads. On kernels with CONFIG_PREEMPT=y, repeated reads can cause preemption to stay disabled, resulting in a SIGSEGV and a kernel BUG triggered by scheduling while atomic. The issue has been fixed by adding a call to put_cpu_var() on successful paths.