<?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, 29 Sep 2026 19:13:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23435 — perf/x86: Move event pointer setup earlier in x86_pmu_enable()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23435</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;perf/x86: Move event pointer setup earlier in x86_pmu_enable()&lt;/p&gt;
&lt;p&gt;A production AMD EPYC system crashed with a NULL pointer dereference
in the PMU NMI handler:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  RIP: x86_perf_event_update+0xc/0xa0
  Call Trace:
   &amp;lt;NMI&amp;gt;
   amd_pmu_v2_handle_irq+0x1a6/0x390
   perf_event_nmi_handler+0x24/0x40&lt;/p&gt;
&lt;p&gt;The faulting instruction is `cmpq $0x0, 0x198(%rdi)` with RDI=0,
corresponding to the `if (unlikely(!hwc-&amp;gt;event_base))` check in
x86_perf_event_update() where hwc = &amp;amp;event-&amp;gt;hw and event is NULL.&lt;/p&gt;
&lt;p&gt;drgn inspection of the vmcore on CPU 106 showed a mismatch between
cpuc-&amp;gt;active_mask and cpuc-&amp;gt;events[]:&lt;/p&gt;
&lt;p&gt;active_mask: 0x1e (bits 1, 2, 3, 4)
  events[1]:   0xff1100136cbd4f38  (valid)
  events[2]:   0x0                 (NULL, but active_mask bit 2 set)
  events[3]:   0xff1100076fd2cf38  (valid)
  events[4]:   0xff1100079e990a90  (valid)&lt;/p&gt;
&lt;p&gt;The event that should occupy events[2] was found in event_list[2]
with hw.idx=2 and hw.state=0x0, confirming x86_pmu_start() had run
(which clears hw.state and sets active_mask) but events[2] was
never populated.&lt;/p&gt;
&lt;p&gt;Another event (event_list[0]) had hw.state=0x7 (STOPPED|UPTODATE|ARCH),
showing it was stopped when the PMU rescheduled events, confirming the
throttle-then-reschedule sequence occurred.&lt;/p&gt;
&lt;p&gt;The root cause is commit 7e772a93eb61 (&amp;#34;perf/x86: Fix NULL event access
and potential PEBS record loss&amp;#34;) which moved the cpuc-&amp;gt;eve…&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;perf/x86: Move event pointer setup earlier in x86_pmu_enable()&lt;/p&gt;
&lt;p&gt;A production AMD EPYC system crashed with a NULL pointer dereference
in the PMU NMI handler:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  RIP: x86_perf_event_update+0xc/0xa0
  Call Trace:
   &amp;lt;NMI&amp;gt;
   amd_pmu_v2_handle_irq+0x1a6/0x390
   perf_event_nmi_handler+0x24/0x40&lt;/p&gt;
&lt;p&gt;The faulting instruction is `cmpq $0x0, 0x198(%rdi)` with RDI=0,
corresponding to the `if (unlikely(!hwc-&amp;gt;event_base))` check in
x86_perf_event_update() where hwc = &amp;amp;event-&amp;gt;hw and event is NULL.&lt;/p&gt;
&lt;p&gt;drgn inspection of the vmcore on CPU 106 showed a mismatch between
cpuc-&amp;gt;active_mask and cpuc-&amp;gt;events[]:&lt;/p&gt;
&lt;p&gt;active_mask: 0x1e (bits 1, 2, 3, 4)
  events[1]:   0xff1100136cbd4f38  (valid)
  events[2]:   0x0                 (NULL, but active_mask bit 2 set)
  events[3]:   0xff1100076fd2cf38  (valid)
  events[4]:   0xff1100079e990a90  (valid)&lt;/p&gt;
&lt;p&gt;The event that should occupy events[2] was found in event_list[2]
with hw.idx=2 and hw.state=0x0, confirming x86_pmu_start() had run
(which clears hw.state and sets active_mask) but events[2] was
never populated.&lt;/p&gt;
&lt;p&gt;Another event (event_list[0]) had hw.state=0x7 (STOPPED|UPTODATE|ARCH),
showing it was stopped when the PMU rescheduled events, confirming the
throttle-then-reschedule sequence occurred.&lt;/p&gt;
&lt;p&gt;The root cause is commit 7e772a93eb61 (&amp;#34;perf/x86: Fix NULL event access
and potential PEBS record loss&amp;#34;) which moved the cpuc-&amp;gt;eve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23435</guid>
    </item>
  </channel>
</rss>
