<?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>Wed, 07 Oct 2026 16:28:36 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13464</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13464</link>
      <description>bdu:2025-13464</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13464</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38252</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38252</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38252</guid>
    </item>
    <item>
      <title>EUVD-2026-346982</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346982</link>
      <description>EUVD-2026-346982</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346982</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38252</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38252</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cxl/ras: Fix CPER handler device confusion&lt;/p&gt;
&lt;p&gt;By inspection, cxl_cper_handle_prot_err() is making a series of fragile
assumptions that can lead to crashes:&lt;/p&gt;
&lt;p&gt;1/ It assumes that endpoints identified in the record are a CXL-type-3
   device, nothing guarantees that.&lt;/p&gt;
&lt;p&gt;2/ It assumes that the device is bound to the cxl_pci driver, nothing
   guarantees that.&lt;/p&gt;
&lt;p&gt;3/ Minor, it holds the device lock over the switch-port tracing for no
   reason as the trace is 100% generated from data in the record.&lt;/p&gt;
&lt;p&gt;Correct those by checking that the PCIe endpoint parents a cxl_memdev
before assuming the format of the driver data, and move the lock to where
it is required. Consequently this also makes the implementation ready for
CXL accelerators that are not bound to cxl_pci.&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;cxl/ras: Fix CPER handler device confusion&lt;/p&gt;
&lt;p&gt;By inspection, cxl_cper_handle_prot_err() is making a series of fragile
assumptions that can lead to crashes:&lt;/p&gt;
&lt;p&gt;1/ It assumes that endpoints identified in the record are a CXL-type-3
   device, nothing guarantees that.&lt;/p&gt;
&lt;p&gt;2/ It assumes that the device is bound to the cxl_pci driver, nothing
   guarantees that.&lt;/p&gt;
&lt;p&gt;3/ Minor, it holds the device lock over the switch-port tracing for no
   reason as the trace is 100% generated from data in the record.&lt;/p&gt;
&lt;p&gt;Correct those by checking that the PCIe endpoint parents a cxl_memdev
before assuming the format of the driver data, and move the lock to where
it is required. Consequently this also makes the implementation ready for
CXL accelerators that are not bound to cxl_pci.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38252</guid>
    </item>
    <item>
      <title>GHSA-r9h8-qv2j-9qwp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r9h8-qv2j-9qwp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cxl/ras: Fix CPER handler device confusion&lt;/p&gt;
&lt;p&gt;By inspection, cxl_cper_handle_prot_err() is making a series of fragile
assumptions that can lead to crashes:&lt;/p&gt;
&lt;p&gt;1/ It assumes that endpoints identified in the record are a CXL-type-3
   device, nothing guarantees that.&lt;/p&gt;
&lt;p&gt;2/ It assumes that the device is bound to the cxl_pci driver, nothing
   guarantees that.&lt;/p&gt;
&lt;p&gt;3/ Minor, it holds the device lock over the switch-port tracing for no
   reason as the trace is 100% generated from data in the record.&lt;/p&gt;
&lt;p&gt;Correct those by checking that the PCIe endpoint parents a cxl_memdev
before assuming the format of the driver data, and move the lock to where
it is required. Consequently this also makes the implementation ready for
CXL accelerators that are not bound to cxl_pci.&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;cxl/ras: Fix CPER handler device confusion&lt;/p&gt;
&lt;p&gt;By inspection, cxl_cper_handle_prot_err() is making a series of fragile
assumptions that can lead to crashes:&lt;/p&gt;
&lt;p&gt;1/ It assumes that endpoints identified in the record are a CXL-type-3
   device, nothing guarantees that.&lt;/p&gt;
&lt;p&gt;2/ It assumes that the device is bound to the cxl_pci driver, nothing
   guarantees that.&lt;/p&gt;
&lt;p&gt;3/ Minor, it holds the device lock over the switch-port tracing for no
   reason as the trace is 100% generated from data in the record.&lt;/p&gt;
&lt;p&gt;Correct those by checking that the PCIe endpoint parents a cxl_memdev
before assuming the format of the driver data, and move the lock to where
it is required. Consequently this also makes the implementation ready for
CXL accelerators that are not bound to cxl_pci.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r9h8-qv2j-9qwp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38252</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38252</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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cxl/ras: Fix CPER handler device confusion By inspection, cxl_cper_handle_prot_err() is making a series of fragile assumptions that can lead to crashes: 1/ It assumes that endpoints identified in the record are a CXL-type-3    device, nothing guarantees that. 2/ It assumes that the device is bound to the cxl_pci driver, nothing    guarantees that. 3/ Minor, it holds the device lock over the switch-port tracing for no    reason as the trace is 100% generated from data in the record. Correct those by checking that the PCIe endpoint parents a cxl_memdev before assuming the format of the driver data, and move the lock to where it is required. Consequently this also makes the implementation ready for CXL accelerators that are not bound to cxl_pci.&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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cxl/ras: Fix CPER handler device confusion By inspection, cxl_cper_handle_prot_err() is making a series of fragile assumptions that can lead to crashes: 1/ It assumes that endpoints identified in the record are a CXL-type-3    device, nothing guarantees that. 2/ It assumes that the device is bound to the cxl_pci driver, nothing    guarantees that. 3/ Minor, it holds the device lock over the switch-port tracing for no    reason as the trace is 100% generated from data in the record. Correct those by checking that the PCIe endpoint parents a cxl_memdev before assuming the format of the driver data, and move the lock to where it is required. Consequently this also makes the implementation ready for CXL accelerators that are not bound to cxl_pci.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38252</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1517 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1517</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1517</guid>
    </item>
  </channel>
</rss>
