<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 14:03:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03968</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03968</link>
      <description>bdu:2026-03968</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03968</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0529 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</link>
      <description>certfr-2025-avi-0529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</guid>
    </item>
    <item>
      <title>EUVD-2026-310802</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310802</link>
      <description>EUVD-2026-310802</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310802</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49781</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49781</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ? hrtimer_start_range_ns+0x141/0x4a0
   ? perf_duration_warn+0x30/0x30
   remote_function+0x4d/0x60
   __flush_smp_call_function_queue+0xc4/0x500
   flush_smp_call_function_queue+0x11d/0x1b0
   do_idle+0x18f/0x2d0
   cpu_startup_entry+0x19/0x20
   start_secondary+0x121/0x160
   secondary_startup_64_no_verify+0xe5/0xeb
   &amp;lt;/TASK&amp;gt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ? hrtimer_start_range_ns+0x141/0x4a0
   ? perf_duration_warn+0x30/0x30
   remote_function+0x4d/0x60
   __flush_smp_call_function_queue+0xc4/0x500
   flush_smp_call_function_queue+0x11d/0x1b0
   do_idle+0x18f/0x2d0
   cpu_startup_entry+0x19/0x20
   start_secondary+0x121/0x160
   secondary_startup_64_no_verify+0xe5/0xeb
   &amp;lt;/TASK&amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49781</guid>
    </item>
    <item>
      <title>GHSA-76hj-mcwf-qj3w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-76hj-mcwf-qj3w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ? hrtimer_start_range_ns+0x141/0x4a0
   ? perf_duration_warn+0x30/0x30
   remote_function+0x4d/0x60
   __flush_smp_call_function_queue+0xc4/0x500
   flush_smp_call_function_queue+0x11d/0x1b0
   do_idle+0x18f/0x2d0
   cpu_startup_entry+0x19/0x20
   start_secondary+0x121/0x160
   secondary_startup_64_no_verify+0xe5/0xeb
   &amp;lt;/TASK&amp;gt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ? hrtimer_start_range_ns+0x141/0x4a0
   ? perf_duration_warn+0x30/0x30
   remote_function+0x4d/0x60
   __flush_smp_call_function_queue+0xc4/0x500
   flush_smp_call_function_queue+0x11d/0x1b0
   do_idle+0x18f/0x2d0
   cpu_startup_entry+0x19/0x20
   start_secondary+0x121/0x160
   secondary_startup_64_no_verify+0xe5/0xeb
   &amp;lt;/TASK&amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-76hj-mcwf-qj3w</guid>
    </item>
    <item>
      <title>OESA-2025-1570 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1570</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A double-free flaw was found in the Linux kernel’s NTFS3 subsystem in how a user triggers remount and umount simultaneously. This flaw allows a local user to crash or potentially escalate their privileges on the system.(CVE-2022-3238)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;amp;gt;events[idx] and cpuc-&amp;amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ?…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A double-free flaw was found in the Linux kernel’s NTFS3 subsystem in how a user triggers remount and umount simultaneously. This flaw allows a local user to crash or potentially escalate their privileges on the system.(CVE-2022-3238)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_all() does:&lt;/p&gt;
&lt;p&gt;if (!test_bit(idx, cpuc-&amp;amp;gt;active_mask))
              continue;&lt;/p&gt;
&lt;p&gt;amd_pmu_enable_event(cpuc-&amp;amp;gt;events[idx]);&lt;/p&gt;
&lt;p&gt;A perf NMI of another event can come between these two steps. Perf NMI
handler internally disables and enables _all_ events, including the one
which nmi-intercepted amd_pmu_enable_all() was in process of enabling.
If that unintentionally enabled event has very low sampling period and
causes immediate successive NMI, causing the event to be throttled,
cpuc-&amp;amp;gt;events[idx] and cpuc-&amp;amp;gt;active_mask gets cleared by x86_pmu_stop().
This will result in amd_pmu_enable_event() getting called with event=NULL
when amd_pmu_enable_all() resumes after handling the NMIs. This causes a
kernel crash:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000198
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  [...]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   amd_pmu_enable_all+0x68/0xb0
   ctx_resched+0xd9/0x150
   event_function+0xb8/0x130
   ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1570</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01966-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01966-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01966-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49781</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49781</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling amd_pmu_enable_all() does:       if (!test_bit(idx, cpuc-&amp;gt;active_mask))               continue;       amd_pmu_enable_event(cpuc-&amp;gt;events[idx]); A perf NMI of another event can come between these two steps. Perf NMI handler internally disables and enables _all_ events, including the one which nmi-intercepted amd_pmu_enable_all() was in process of enabling. If that unintentionally enabled event has very low sampling period and causes immediate successive NMI, causing the event to be throttled, cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop(). This will result in amd_pmu_enable_event() getting called with event=NULL when amd_pmu_enable_all() resumes after handling the NMIs. This causes a kernel crash:   BUG: kernel NULL pointer dereference, address: 0000000000000198   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   [...]   Call Trace:    &amp;lt;TASK&amp;gt;    amd_pmu_enable_all+0x68/0xb0    ctx_resched+0xd9/0x150    event_function+0xb8/0x130    ? hrtimer_start_range_ns+0x141/0x4a0    ? perf_duration_warn+0x30/0x30    remote_function+0x4d/0x60    __flush_smp_call_function_queue+0xc4/0x500    flush_smp_call_function_queue+0x11d/0x1b0    do_idle+0x18f/0x2d0    cpu_startup_entry+0x19/0x20    start_secondary+0x121/0x160    secondary_startup_64_no_verify+0xe5/0xeb    &amp;lt;/TASK&amp;gt; amd_p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling amd_pmu_enable_all() does:       if (!test_bit(idx, cpuc-&amp;gt;active_mask))               continue;       amd_pmu_enable_event(cpuc-&amp;gt;events[idx]); A perf NMI of another event can come between these two steps. Perf NMI handler internally disables and enables _all_ events, including the one which nmi-intercepted amd_pmu_enable_all() was in process of enabling. If that unintentionally enabled event has very low sampling period and causes immediate successive NMI, causing the event to be throttled, cpuc-&amp;gt;events[idx] and cpuc-&amp;gt;active_mask gets cleared by x86_pmu_stop(). This will result in amd_pmu_enable_event() getting called with event=NULL when amd_pmu_enable_all() resumes after handling the NMIs. This causes a kernel crash:   BUG: kernel NULL pointer dereference, address: 0000000000000198   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   [...]   Call Trace:    &amp;lt;TASK&amp;gt;    amd_pmu_enable_all+0x68/0xb0    ctx_resched+0xd9/0x150    event_function+0xb8/0x130    ? hrtimer_start_range_ns+0x141/0x4a0    ? perf_duration_warn+0x30/0x30    remote_function+0x4d/0x60    __flush_smp_call_function_queue+0xc4/0x500    flush_smp_call_function_queue+0x11d/0x1b0    do_idle+0x18f/0x2d0    cpu_startup_entry+0x19/0x20    start_secondary+0x121/0x160    secondary_startup_64_no_verify+0xe5/0xeb    &amp;lt;/TASK&amp;gt; amd_p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49781</guid>
    </item>
  </channel>
</rss>
