<?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>Fri, 02 Oct 2026 19:35:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53313</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53313</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53313</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-364378</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364378</link>
      <description>EUVD-2026-364378</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364378</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53313</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53313</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths&lt;/p&gt;
&lt;p&gt;In dc_dmub_srv_log_diagnostic_data() and
dc_dmub_srv_enable_dpia_trace().&lt;/p&gt;
&lt;p&gt;Both functions check:&lt;/p&gt;
&lt;p&gt;if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub)&lt;/p&gt;
&lt;p&gt;and then call DC_LOG_ERROR() inside that block.&lt;/p&gt;
&lt;p&gt;DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if
dc_dmub_srv is NULL, the logging itself can dereference a
NULL pointer and cause a crash.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the checks.&lt;/p&gt;
&lt;p&gt;First check if dc_dmub_srv is NULL and return immediately.
Then check dc_dmub_srv-&amp;gt;dmub and log the error only when
dc_dmub_srv is valid.&lt;/p&gt;
&lt;p&gt;Fixes the below:
../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961)
../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&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/amd/display: Avoid NULL dereference in dc_dmub_srv error paths&lt;/p&gt;
&lt;p&gt;In dc_dmub_srv_log_diagnostic_data() and
dc_dmub_srv_enable_dpia_trace().&lt;/p&gt;
&lt;p&gt;Both functions check:&lt;/p&gt;
&lt;p&gt;if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub)&lt;/p&gt;
&lt;p&gt;and then call DC_LOG_ERROR() inside that block.&lt;/p&gt;
&lt;p&gt;DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if
dc_dmub_srv is NULL, the logging itself can dereference a
NULL pointer and cause a crash.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the checks.&lt;/p&gt;
&lt;p&gt;First check if dc_dmub_srv is NULL and return immediately.
Then check dc_dmub_srv-&amp;gt;dmub and log the error only when
dc_dmub_srv is valid.&lt;/p&gt;
&lt;p&gt;Fixes the below:
../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961)
../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53313</guid>
    </item>
    <item>
      <title>GHSA-2885-rcqv-3jp6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2885-rcqv-3jp6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths&lt;/p&gt;
&lt;p&gt;In dc_dmub_srv_log_diagnostic_data() and
dc_dmub_srv_enable_dpia_trace().&lt;/p&gt;
&lt;p&gt;Both functions check:&lt;/p&gt;
&lt;p&gt;if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub)&lt;/p&gt;
&lt;p&gt;and then call DC_LOG_ERROR() inside that block.&lt;/p&gt;
&lt;p&gt;DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if
dc_dmub_srv is NULL, the logging itself can dereference a
NULL pointer and cause a crash.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the checks.&lt;/p&gt;
&lt;p&gt;First check if dc_dmub_srv is NULL and return immediately.
Then check dc_dmub_srv-&amp;gt;dmub and log the error only when
dc_dmub_srv is valid.&lt;/p&gt;
&lt;p&gt;Fixes the below:
../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961)
../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&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/amd/display: Avoid NULL dereference in dc_dmub_srv error paths&lt;/p&gt;
&lt;p&gt;In dc_dmub_srv_log_diagnostic_data() and
dc_dmub_srv_enable_dpia_trace().&lt;/p&gt;
&lt;p&gt;Both functions check:&lt;/p&gt;
&lt;p&gt;if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub)&lt;/p&gt;
&lt;p&gt;and then call DC_LOG_ERROR() inside that block.&lt;/p&gt;
&lt;p&gt;DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if
dc_dmub_srv is NULL, the logging itself can dereference a
NULL pointer and cause a crash.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the checks.&lt;/p&gt;
&lt;p&gt;First check if dc_dmub_srv is NULL and return immediately.
Then check dc_dmub_srv-&amp;gt;dmub and log the error only when
dc_dmub_srv is valid.&lt;/p&gt;
&lt;p&gt;Fixes the below:
../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961)
../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2885-rcqv-3jp6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53313 — drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53313</link>
      <description>msrc_CVE-2026-53313</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53313</guid>
    </item>
    <item>
      <title>OESA-2026-3454 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3454</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: remove xfs_attr_leaf_hasname&lt;/p&gt;
&lt;p&gt;The calling convention of xfs_attr_leaf_hasname() is problematic, because
it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer
when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a
non-NULL buffer pointer for an already released buffer when
xfs_attr3_leaf_lookup_int fails with other error values.&lt;/p&gt;
&lt;p&gt;Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so
that the buffer release code is done by each caller of
xfs_attr3_leaf_read.(CVE-2026-43153)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kexec: Disable KCOV instrumentation after load_segments()&lt;/p&gt;
&lt;p&gt;The load_segments() function changes segment registers, invalidating GS base
(which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any
subsequent instrumented C code call (e.g. native_gdt_invalidate()) begins
crashing the kernel in an endless loop.&lt;/p&gt;
&lt;p&gt;To reproduce the problem, it&amp;amp;apos;s sufficient to do kexec on a KCOV-instrumented
kernel:&lt;/p&gt;
&lt;p&gt;$ kexec -l /boot/otherKernel
  $ kexec -e&lt;/p&gt;
&lt;p&gt;The real-world context for this problem is enabling crash dump collection in
syzkaller. For this, the tool loads a panic kernel before fuzzing and then
calls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC
and CONFIG_KCOV to be enabled simultaneously.&lt;/p&gt;
&lt;p&gt;Adding safeguard…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: remove xfs_attr_leaf_hasname&lt;/p&gt;
&lt;p&gt;The calling convention of xfs_attr_leaf_hasname() is problematic, because
it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer
when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a
non-NULL buffer pointer for an already released buffer when
xfs_attr3_leaf_lookup_int fails with other error values.&lt;/p&gt;
&lt;p&gt;Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so
that the buffer release code is done by each caller of
xfs_attr3_leaf_read.(CVE-2026-43153)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kexec: Disable KCOV instrumentation after load_segments()&lt;/p&gt;
&lt;p&gt;The load_segments() function changes segment registers, invalidating GS base
(which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any
subsequent instrumented C code call (e.g. native_gdt_invalidate()) begins
crashing the kernel in an endless loop.&lt;/p&gt;
&lt;p&gt;To reproduce the problem, it&amp;amp;apos;s sufficient to do kexec on a KCOV-instrumented
kernel:&lt;/p&gt;
&lt;p&gt;$ kexec -l /boot/otherKernel
  $ kexec -e&lt;/p&gt;
&lt;p&gt;The real-world context for this problem is enabling crash dump collection in
syzkaller. For this, the tool loads a panic kernel before fuzzing and then
calls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC
and CONFIG_KCOV to be enabled simultaneously.&lt;/p&gt;
&lt;p&gt;Adding safeguard…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3454</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-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/opensuse-su-2026:21555-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53313</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53313</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 201 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace(). Both functions check:   if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub) and then call DC_LOG_ERROR() inside that block. DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL pointer and cause a crash. Fix this by splitting the checks. First check if dc_dmub_srv is NULL and return immediately. Then check dc_dmub_srv-&amp;gt;dmub and log the error only when dc_dmub_srv is valid. Fixes the below: ../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961) ../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&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 201 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace(). Both functions check:   if (!dc_dmub_srv || !dc_dmub_srv-&amp;gt;dmub) and then call DC_LOG_ERROR() inside that block. DC_LOG_ERROR() uses dc_dmub_srv-&amp;gt;ctx internally. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL pointer and cause a crash. Fix this by splitting the checks. First check if dc_dmub_srv is NULL and return immediately. Then check dc_dmub_srv-&amp;gt;dmub and log the error only when dc_dmub_srv is valid. Fixes the below: ../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 961) ../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed &amp;#39;dc_dmub_srv&amp;#39; could be null (see line 1166)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53313</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2119</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, einen Denial of Service zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, einen Denial of Service zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2119</guid>
    </item>
  </channel>
</rss>
