https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:45:26 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04861 bdu:2026-04861 https://cve.radiocsirt.org/vuln/bdu:2026-04861 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/euvd-2026-311120 EUVD-2026-311120 https://cve.radiocsirt.org/vuln/euvd-2026-311120 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50261 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()</p> <p>With clang&#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:</p> <p>drivers/gpu/drm/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types init…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()</p> <p>With clang&#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:</p> <p>drivers/gpu/drm/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types init…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50261 https://cve.radiocsirt.org/vuln/ghsa-578g-xfmh-7xmp <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()</p> <p>With clang&#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:</p> <p>drivers/gpu/drm/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types init…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()</p> <p>With clang&#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:</p> <p>drivers/gpu/drm/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types init…</p> https://cve.radiocsirt.org/vuln/ghsa-578g-xfmh-7xmp https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50261 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 158 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid() With clang&#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/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types initial…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 158 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid() With clang&#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/sti/sti_hda.c:637:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_hda_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_dvo.c:376:16: error: incompatible function pointer types initializing &#39;enum drm_mode_status (*)(struct drm_connector *, struct drm_display_mode *)&#39; with an expression of type &#39;int (struct drm_connector *, struct drm_display_mode *)&#39; [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = sti_dvo_connector_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/sti/sti_hdmi.c:1035:16: error: incompatible function pointer types initial…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50261 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053