<?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>Mon, 05 Oct 2026 10:24:30 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03927</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03927</link>
      <description>bdu:2026-03927</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03927</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-309855</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309855</link>
      <description>EUVD-2026-309855</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309855</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47647</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47647</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: qcom: ipq8074: fix PCI-E clock oops&lt;/p&gt;
&lt;p&gt;Fix PCI-E clock related kernel oops that are caused by a missing clock
parent.&lt;/p&gt;
&lt;p&gt;pcie0_rchng_clk_src has num_parents set to 2 but only one parent is
actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined.
This will cause the kernel to panic on a NULL pointer in
clk_core_get_parent_by_index().&lt;/p&gt;
&lt;p&gt;So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent
data.
Since there is already an existing static const char * const gcc_xo_gpll0[]
used to provide the same parents via parent_names convert those users to
clk_parent_data as well.&lt;/p&gt;
&lt;p&gt;Without this earlycon is needed to even catch the OOPS as it will reset
the board before serial is initialized with the following:&lt;/p&gt;
&lt;p&gt;[    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000
[    0.232322] Mem abort info:
[    0.239094]   ESR = 0x96000004
[    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.244908]   SET = 0, FnV = 0
[    0.250377]   EA = 0, S1PTW = 0
[    0.253236]   FSC = 0x04: level 0 translation fault
[    0.256277] Data abort info:
[    0.261141]   ISV = 0, ISS = 0x00000004
[    0.264262]   CM = 0, WnR = 0
[    0.267820] [0000a00000000000] address between user and kernel address ranges
[    0.270954] Internal error: Oops: 96000004 [#1] SMP
[    0.278067] Modules linked in:
[    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0
[    0.285882] Har…&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;clk: qcom: ipq8074: fix PCI-E clock oops&lt;/p&gt;
&lt;p&gt;Fix PCI-E clock related kernel oops that are caused by a missing clock
parent.&lt;/p&gt;
&lt;p&gt;pcie0_rchng_clk_src has num_parents set to 2 but only one parent is
actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined.
This will cause the kernel to panic on a NULL pointer in
clk_core_get_parent_by_index().&lt;/p&gt;
&lt;p&gt;So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent
data.
Since there is already an existing static const char * const gcc_xo_gpll0[]
used to provide the same parents via parent_names convert those users to
clk_parent_data as well.&lt;/p&gt;
&lt;p&gt;Without this earlycon is needed to even catch the OOPS as it will reset
the board before serial is initialized with the following:&lt;/p&gt;
&lt;p&gt;[    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000
[    0.232322] Mem abort info:
[    0.239094]   ESR = 0x96000004
[    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.244908]   SET = 0, FnV = 0
[    0.250377]   EA = 0, S1PTW = 0
[    0.253236]   FSC = 0x04: level 0 translation fault
[    0.256277] Data abort info:
[    0.261141]   ISV = 0, ISS = 0x00000004
[    0.264262]   CM = 0, WnR = 0
[    0.267820] [0000a00000000000] address between user and kernel address ranges
[    0.270954] Internal error: Oops: 96000004 [#1] SMP
[    0.278067] Modules linked in:
[    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0
[    0.285882] Har…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47647</guid>
    </item>
    <item>
      <title>GHSA-wx79-2q2c-86qm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wx79-2q2c-86qm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: qcom: ipq8074: fix PCI-E clock oops&lt;/p&gt;
&lt;p&gt;Fix PCI-E clock related kernel oops that are caused by a missing clock
parent.&lt;/p&gt;
&lt;p&gt;pcie0_rchng_clk_src has num_parents set to 2 but only one parent is
actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined.
This will cause the kernel to panic on a NULL pointer in
clk_core_get_parent_by_index().&lt;/p&gt;
&lt;p&gt;So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent
data.
Since there is already an existing static const char * const gcc_xo_gpll0[]
used to provide the same parents via parent_names convert those users to
clk_parent_data as well.&lt;/p&gt;
&lt;p&gt;Without this earlycon is needed to even catch the OOPS as it will reset
the board before serial is initialized with the following:&lt;/p&gt;
&lt;p&gt;[    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000
[    0.232322] Mem abort info:
[    0.239094]   ESR = 0x96000004
[    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.244908]   SET = 0, FnV = 0
[    0.250377]   EA = 0, S1PTW = 0
[    0.253236]   FSC = 0x04: level 0 translation fault
[    0.256277] Data abort info:
[    0.261141]   ISV = 0, ISS = 0x00000004
[    0.264262]   CM = 0, WnR = 0
[    0.267820] [0000a00000000000] address between user and kernel address ranges
[    0.270954] Internal error: Oops: 96000004 [#1] SMP
[    0.278067] Modules linked in:
[    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0
[    0.285882] Har…&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;clk: qcom: ipq8074: fix PCI-E clock oops&lt;/p&gt;
&lt;p&gt;Fix PCI-E clock related kernel oops that are caused by a missing clock
parent.&lt;/p&gt;
&lt;p&gt;pcie0_rchng_clk_src has num_parents set to 2 but only one parent is
actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined.
This will cause the kernel to panic on a NULL pointer in
clk_core_get_parent_by_index().&lt;/p&gt;
&lt;p&gt;So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent
data.
Since there is already an existing static const char * const gcc_xo_gpll0[]
used to provide the same parents via parent_names convert those users to
clk_parent_data as well.&lt;/p&gt;
&lt;p&gt;Without this earlycon is needed to even catch the OOPS as it will reset
the board before serial is initialized with the following:&lt;/p&gt;
&lt;p&gt;[    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000
[    0.232322] Mem abort info:
[    0.239094]   ESR = 0x96000004
[    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.244908]   SET = 0, FnV = 0
[    0.250377]   EA = 0, S1PTW = 0
[    0.253236]   FSC = 0x04: level 0 translation fault
[    0.256277] Data abort info:
[    0.261141]   ISV = 0, ISS = 0x00000004
[    0.264262]   CM = 0, WnR = 0
[    0.267820] [0000a00000000000] address between user and kernel address ranges
[    0.270954] Internal error: Oops: 96000004 [#1] SMP
[    0.278067] Modules linked in:
[    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0
[    0.285882] Har…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wx79-2q2c-86qm</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47647</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47647</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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: fix PCI-E clock oops Fix PCI-E clock related kernel oops that are caused by a missing clock parent. pcie0_rchng_clk_src has num_parents set to 2 but only one parent is actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined. This will cause the kernel to panic on a NULL pointer in clk_core_get_parent_by_index(). So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent data. Since there is already an existing static const char * const gcc_xo_gpll0[] used to provide the same parents via parent_names convert those users to clk_parent_data as well. Without this earlycon is needed to even catch the OOPS as it will reset the board before serial is initialized with the following: [    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000 [    0.232322] Mem abort info: [    0.239094]   ESR = 0x96000004 [    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits [    0.244908]   SET = 0, FnV = 0 [    0.250377]   EA = 0, S1PTW = 0 [    0.253236]   FSC = 0x04: level 0 translation fault [    0.256277] Data abort info: [    0.261141]   ISV = 0, ISS = 0x00000004 [    0.264262]   CM = 0, WnR = 0 [    0.267820] [0000a00000000000] address between user and kernel address ranges [    0.270954] Internal error: Oops: 96000004 [#1] SMP [    0.278067] Modules linked in: [    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0 [    0.285882] Hardware…&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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: fix PCI-E clock oops Fix PCI-E clock related kernel oops that are caused by a missing clock parent. pcie0_rchng_clk_src has num_parents set to 2 but only one parent is actually set via parent_hws, it should also have &amp;#34;XO&amp;#34; defined. This will cause the kernel to panic on a NULL pointer in clk_core_get_parent_by_index(). So, to fix this utilize clk_parent_data to provide gcc_xo_gpll0 parent data. Since there is already an existing static const char * const gcc_xo_gpll0[] used to provide the same parents via parent_names convert those users to clk_parent_data as well. Without this earlycon is needed to even catch the OOPS as it will reset the board before serial is initialized with the following: [    0.232279] Unable to handle kernel paging request at virtual address 0000a00000000000 [    0.232322] Mem abort info: [    0.239094]   ESR = 0x96000004 [    0.241778]   EC = 0x25: DABT (current EL), IL = 32 bits [    0.244908]   SET = 0, FnV = 0 [    0.250377]   EA = 0, S1PTW = 0 [    0.253236]   FSC = 0x04: level 0 translation fault [    0.256277] Data abort info: [    0.261141]   ISV = 0, ISS = 0x00000004 [    0.264262]   CM = 0, WnR = 0 [    0.267820] [0000a00000000000] address between user and kernel address ranges [    0.270954] Internal error: Oops: 96000004 [#1] SMP [    0.278067] Modules linked in: [    0.282751] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.10 #0 [    0.285882] Hardware…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47647</guid>
    </item>
  </channel>
</rss>
