<?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>Fri, 16 Oct 2026 07:52:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37878 — perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-37878</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/core: Fix WARN_ON(!ctx) in __free_event() for partial init&lt;/p&gt;
&lt;p&gt;Move the get_ctx(child_ctx) call and the child_event-&amp;gt;ctx assignment to
occur immediately after the child event is allocated. Ensure that
child_event-&amp;gt;ctx is non-NULL before any subsequent error path within
inherit_event calls free_event(), satisfying the assumptions of the
cleanup code.&lt;/p&gt;
&lt;p&gt;Details:&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no clear Fixes tag, because this bug is a side-effect of
multiple interacting commits over time (up to 15 years old), not
a single regression.&lt;/p&gt;
&lt;p&gt;The code initially incremented refcount then assigned context
immediately after the child_event was created. Later, an early
validity check for child_event was added before the
refcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was
added, assuming event-&amp;gt;ctx is valid if the pmu_ctx is valid.
The problem is that the WARN_ON_ONCE() could trigger after the initial
check passed but before child_event-&amp;gt;ctx was assigned, violating its
precondition. The solution is to assign child_event-&amp;gt;ctx right after
its initial validation. This ensures the context exists for any
subsequent checks or cleanup routines, resolving the WARN_ON_ONCE().&lt;/p&gt;
&lt;p&gt;To resolve it, defer the refcount update and child_event-&amp;gt;ctx assignment
directly after child_event-&amp;gt;pmu_ctx is set but before checking if the
parent event is orphaned. The cleanup routine depends on
event-&amp;gt;pmu_ctx being non-NULL before it verifies event-&amp;gt;ctx is
n…&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/core: Fix WARN_ON(!ctx) in __free_event() for partial init&lt;/p&gt;
&lt;p&gt;Move the get_ctx(child_ctx) call and the child_event-&amp;gt;ctx assignment to
occur immediately after the child event is allocated. Ensure that
child_event-&amp;gt;ctx is non-NULL before any subsequent error path within
inherit_event calls free_event(), satisfying the assumptions of the
cleanup code.&lt;/p&gt;
&lt;p&gt;Details:&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no clear Fixes tag, because this bug is a side-effect of
multiple interacting commits over time (up to 15 years old), not
a single regression.&lt;/p&gt;
&lt;p&gt;The code initially incremented refcount then assigned context
immediately after the child_event was created. Later, an early
validity check for child_event was added before the
refcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was
added, assuming event-&amp;gt;ctx is valid if the pmu_ctx is valid.
The problem is that the WARN_ON_ONCE() could trigger after the initial
check passed but before child_event-&amp;gt;ctx was assigned, violating its
precondition. The solution is to assign child_event-&amp;gt;ctx right after
its initial validation. This ensures the context exists for any
subsequent checks or cleanup routines, resolving the WARN_ON_ONCE().&lt;/p&gt;
&lt;p&gt;To resolve it, defer the refcount update and child_event-&amp;gt;ctx assignment
directly after child_event-&amp;gt;pmu_ctx is set but before checking if the
parent event is orphaned. The cleanup routine depends on
event-&amp;gt;pmu_ctx being non-NULL before it verifies event-&amp;gt;ctx is
n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-37878</guid>
    </item>
    <item>
      <title>USN-7594-1 — linux, linux-gcp, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7594-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - Intel Management Engine Interface driver;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Synopsys DesignWare PCIe PMU;
  - Mellanox platform drivers;
  - PWM drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  -…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - Intel Management Engine Interface driver;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Synopsys DesignWare PCIe PMU;
  - Mellanox platform drivers;
  - PWM drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  -…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7594-1</guid>
    </item>
  </channel>
</rss>
