<?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 15:51:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03064</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03064</link>
      <description>bdu:2026-03064</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03064</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38636</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38636</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-2025-38636</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1203 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</link>
      <description>certfr-2026-avi-1203</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1203</guid>
    </item>
    <item>
      <title>EUVD-2026-314693</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314693</link>
      <description>EUVD-2026-314693</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314693</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38636</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38636</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&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;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38636</guid>
    </item>
    <item>
      <title>GHSA-xg28-vm4v-pcgp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xg28-vm4v-pcgp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&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;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xg28-vm4v-pcgp</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38636 — rv: Use strings in da monitors tracepoints</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38636</link>
      <description>msrc_CVE-2025-38636</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38636</guid>
    </item>
    <item>
      <title>OESA-2025-2802 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2802</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2802</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38636</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38636</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 125 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rv: Use strings in da monitors tracepoints Using DA monitors tracepoints with KASAN enabled triggers the following warning:  BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0  Read of size 32 at addr ffffffffaada8980 by task ...  Call Trace:   &amp;lt;TASK&amp;gt;  [...]   do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0   ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10   ? trace_event_sncid+0x83/0x200   trace_event_sncid+0x163/0x200  [...]  The buggy address belongs to the variable:   automaton_snep+0x4e0/0x5e0 This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g. the next automaton&amp;#39;s data in this case). The error is harmless as, while printing the string, we stop at the null terminator, but it should still be fixed. Use the __string facilities while defining the tracepoints to avoid reading out of bound memory.&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 125 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rv: Use strings in da monitors tracepoints Using DA monitors tracepoints with KASAN enabled triggers the following warning:  BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0  Read of size 32 at addr ffffffffaada8980 by task ...  Call Trace:   &amp;lt;TASK&amp;gt;  [...]   do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0   ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10   ? trace_event_sncid+0x83/0x200   trace_event_sncid+0x163/0x200  [...]  The buggy address belongs to the variable:   automaton_snep+0x4e0/0x5e0 This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g. the next automaton&amp;#39;s data in this case). The error is harmless as, while printing the string, we stop at the null terminator, but it should still be fixed. Use the __string facilities while defining the tracepoints to avoid reading out of bound memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38636</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und Privilegieneskalation</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</guid>
    </item>
  </channel>
</rss>
