<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 17:25:45 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2026-AVI-0108 — 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://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108</link>
      <description>CERTFR-2026-AVI-0108</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108</guid>
    </item>
    <item>
      <title>bdu:2026-08960</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-08960</link>
      <description>bdu:2026-08960</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-08960</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50844</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50844</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback&lt;/p&gt;
&lt;p&gt;With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run time,
which manifests as either a kernel panic or thread getting killed. A
proposed warning in clang aims to catch these at compile time, which
reveals:&lt;/p&gt;
&lt;p&gt;drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]
          .odn_edit_dpm_table      = smu_od_edit_dpm_table,
                                     ^~~~~~~~~~~~~~~~~~~~~
  1 error generated.&lt;/p&gt;
&lt;p&gt;There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct
amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One
has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the
other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls
-&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and
pp_odn_edit_dpm…&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;drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback&lt;/p&gt;
&lt;p&gt;With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run time,
which manifests as either a kernel panic or thread getting killed. A
proposed warning in clang aims to catch these at compile time, which
reveals:&lt;/p&gt;
&lt;p&gt;drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]
          .odn_edit_dpm_table      = smu_od_edit_dpm_table,
                                     ^~~~~~~~~~~~~~~~~~~~~
  1 error generated.&lt;/p&gt;
&lt;p&gt;There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct
amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One
has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the
other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls
-&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and
pp_odn_edit_dpm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2022-50844</guid>
    </item>
    <item>
      <title>GHSA-mmx6-rf97-26wh</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mmx6-rf97-26wh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback&lt;/p&gt;
&lt;p&gt;With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run time,
which manifests as either a kernel panic or thread getting killed. A
proposed warning in clang aims to catch these at compile time, which
reveals:&lt;/p&gt;
&lt;p&gt;drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]
          .odn_edit_dpm_table      = smu_od_edit_dpm_table,
                                     ^~~~~~~~~~~~~~~~~~~~~
  1 error generated.&lt;/p&gt;
&lt;p&gt;There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct
amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One
has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the
other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls
-&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and
pp_odn_edit_dpm…&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;drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback&lt;/p&gt;
&lt;p&gt;With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run time,
which manifests as either a kernel panic or thread getting killed. A
proposed warning in clang aims to catch these at compile time, which
reveals:&lt;/p&gt;
&lt;p&gt;drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]
          .odn_edit_dpm_table      = smu_od_edit_dpm_table,
                                     ^~~~~~~~~~~~~~~~~~~~~
  1 error generated.&lt;/p&gt;
&lt;p&gt;There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct
amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One
has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the
other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls
-&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and
pp_odn_edit_dpm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mmx6-rf97-26wh</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:0263-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://vulnerability.circl.lu/vuln/suse-su-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50844</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50844</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. A proposed warning in clang aims to catch these at compile time, which reveals:   drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]           .odn_edit_dpm_table      = smu_od_edit_dpm_table,                                      ^~~~~~~~~~~~~~~~~~~~~   1 error generated. There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls -&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and pp_odn_edit_dpm_tab…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. A proposed warning in clang aims to catch these at compile time, which reveals:   drivers/gpu/drm/amd/amdgpu/../pm/swsmu/amdgpu_smu.c:3008:29: error: incompatible function pointer types initializing &amp;#39;int (*)(void *, uint32_t, long *, uint32_t)&amp;#39; (aka &amp;#39;int (*)(void *, unsigned int, long *, unsigned int)&amp;#39;) with an expression of type &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, uint32_t)&amp;#39; (aka &amp;#39;int (void *, enum PP_OD_DPM_TABLE_COMMAND, long *, unsigned int)&amp;#39;) [-Werror,-Wincompatible-function-pointer-types-strict]           .odn_edit_dpm_table      = smu_od_edit_dpm_table,                                      ^~~~~~~~~~~~~~~~~~~~~   1 error generated. There are only two implementations of -&amp;gt;odn_edit_dpm_table() in &amp;#39;struct amd_pm_funcs&amp;#39;: smu_od_edit_dpm_table() and pp_odn_edit_dpm_table(). One has a second parameter type of &amp;#39;enum PP_OD_DPM_TABLE_COMMAND&amp;#39; and the other uses &amp;#39;u32&amp;#39;. Ultimately, smu_od_edit_dpm_table() calls -&amp;gt;od_edit_dpm_table() from &amp;#39;struct pptable_funcs&amp;#39; and pp_odn_edit_dpm_tab…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50844</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2941 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2941</link>
      <description>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2941</guid>
    </item>
  </channel>
</rss>
