<?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 21:41:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14140</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-14140</link>
      <description>bdu:2025-14140</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-14140</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-50238</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-50238</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-50238</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-320723</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320723</link>
      <description>EUVD-2026-320723</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320723</guid>
    </item>
    <item>
      <title>fkie_cve-2024-50238</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-50238</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend&lt;/p&gt;
&lt;p&gt;Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;)
removed most users of the platform device driver data from the
qcom-qmp-usb driver, but mistakenly also removed the initialisation
despite the data still being used in the runtime PM callbacks. This bug
was later reproduced when the driver was copied to create the qmp-usbc
driver.&lt;/p&gt;
&lt;p&gt;Restore the driver data initialisation at probe to avoid a NULL-pointer
dereference on runtime suspend.&lt;/p&gt;
&lt;p&gt;Apparently no one uses runtime PM, which currently needs to be enabled
manually through sysfs, with these drivers.&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;phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend&lt;/p&gt;
&lt;p&gt;Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;)
removed most users of the platform device driver data from the
qcom-qmp-usb driver, but mistakenly also removed the initialisation
despite the data still being used in the runtime PM callbacks. This bug
was later reproduced when the driver was copied to create the qmp-usbc
driver.&lt;/p&gt;
&lt;p&gt;Restore the driver data initialisation at probe to avoid a NULL-pointer
dereference on runtime suspend.&lt;/p&gt;
&lt;p&gt;Apparently no one uses runtime PM, which currently needs to be enabled
manually through sysfs, with these drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-50238</guid>
    </item>
    <item>
      <title>GHSA-9fm4-j993-vwrj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9fm4-j993-vwrj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend&lt;/p&gt;
&lt;p&gt;Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;)
removed most users of the platform device driver data from the
qcom-qmp-usb driver, but mistakenly also removed the initialisation
despite the data still being used in the runtime PM callbacks. This bug
was later reproduced when the driver was copied to create the qmp-usbc
driver.&lt;/p&gt;
&lt;p&gt;Restore the driver data initialisation at probe to avoid a NULL-pointer
dereference on runtime suspend.&lt;/p&gt;
&lt;p&gt;Apparently no one uses runtime PM, which currently needs to be enabled
manually through sysfs, with these drivers.&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;phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend&lt;/p&gt;
&lt;p&gt;Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;)
removed most users of the platform device driver data from the
qcom-qmp-usb driver, but mistakenly also removed the initialisation
despite the data still being used in the runtime PM callbacks. This bug
was later reproduced when the driver was copied to create the qmp-usbc
driver.&lt;/p&gt;
&lt;p&gt;Restore the driver data initialisation at probe to avoid a NULL-pointer
dereference on runtime suspend.&lt;/p&gt;
&lt;p&gt;Apparently no one uses runtime PM, which currently needs to be enabled
manually through sysfs, with these drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9fm4-j993-vwrj</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50238</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50238</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 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;) removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usbc driver. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers.&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 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend Commit 413db06c05e7 (&amp;#34;phy: qcom-qmp-usb: clean up probe initialisation&amp;#34;) removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usbc driver. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50238</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3397 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3397</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3397</guid>
    </item>
  </channel>
</rss>
