<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 05:40:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64070 — powerpc/hv-gpci: fix preempt count leak in sysfs show paths</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64070</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/hv-gpci: fix preempt count leak in sysfs show paths&lt;/p&gt;
&lt;p&gt;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 &amp;#39;out:&amp;#39; label. Every successful read leaks
one preempt_disable():&lt;/p&gt;
&lt;p&gt;processor_bus_topology_show()
  processor_config_show()
  affinity_domain_via_virtual_processor_show()
  affinity_domain_via_domain_show()&lt;/p&gt;
&lt;p&gt;(affinity_domain_via_partition_show() was already correct.)&lt;/p&gt;
&lt;p&gt;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
&amp;#39;BUG: scheduling while atomic&amp;#39; in call_usermodehelper_exec -&amp;gt;
wait_for_completion_state -&amp;gt; schedule:&lt;/p&gt;
&lt;p&gt;BUG: scheduling while atomic: &amp;lt;task&amp;gt;/&amp;lt;pid&amp;gt;/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&lt;/p&gt;
&lt;p&gt;Add an out_success label that calls put_cpu_var() before returning
the byte count, mirroring affinity_domain_via_partition_show().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/hv-gpci: fix preempt count leak in sysfs show paths&lt;/p&gt;
&lt;p&gt;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 &amp;#39;out:&amp;#39; label. Every successful read leaks
one preempt_disable():&lt;/p&gt;
&lt;p&gt;processor_bus_topology_show()
  processor_config_show()
  affinity_domain_via_virtual_processor_show()
  affinity_domain_via_domain_show()&lt;/p&gt;
&lt;p&gt;(affinity_domain_via_partition_show() was already correct.)&lt;/p&gt;
&lt;p&gt;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
&amp;#39;BUG: scheduling while atomic&amp;#39; in call_usermodehelper_exec -&amp;gt;
wait_for_completion_state -&amp;gt; schedule:&lt;/p&gt;
&lt;p&gt;BUG: scheduling while atomic: &amp;lt;task&amp;gt;/&amp;lt;pid&amp;gt;/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&lt;/p&gt;
&lt;p&gt;Add an out_success label that calls put_cpu_var() before returning
the byte count, mirroring affinity_domain_via_partition_show().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64070</guid>
    </item>
  </channel>
</rss>
