<?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>Thu, 08 Oct 2026 09:36:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13462</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13462</link>
      <description>bdu:2025-13462</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13462</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38327</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38327</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38327</guid>
    </item>
    <item>
      <title>EUVD-2026-314543</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314543</link>
      <description>EUVD-2026-314543</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314543</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38327</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38327</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fgraph: Do not enable function_graph tracer when setting funcgraph-args&lt;/p&gt;
&lt;p&gt;When setting the funcgraph-args option when function graph tracer is net
enabled, it incorrectly enables it. Worse, it unregisters itself when it
was never registered. Then when it gets enabled again, it will register
itself a second time causing a WARNing.&lt;/p&gt;
&lt;p&gt;~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args
 ~# head -20 /sys/kernel/tracing/trace
 # tracer: nop
 #
 # entries-in-buffer/entries-written: 813/26317372   #P:8
 #
 #                                _-----=&amp;gt; irqs-off/BH-disabled
 #                               / _----=&amp;gt; need-resched
 #                              | / _---=&amp;gt; hardirq/softirq
 #                              || / _--=&amp;gt; preempt-depth
 #                              ||| / _-=&amp;gt; migrate-disable
 #                              |||| /     delay
 #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
 #              | |         |   |||||     |         |
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |          fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |          tmigr_cpu_deactivate(nextexp=357988000000) {
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |            _raw_spin_lock(lock=0xf…&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;fgraph: Do not enable function_graph tracer when setting funcgraph-args&lt;/p&gt;
&lt;p&gt;When setting the funcgraph-args option when function graph tracer is net
enabled, it incorrectly enables it. Worse, it unregisters itself when it
was never registered. Then when it gets enabled again, it will register
itself a second time causing a WARNing.&lt;/p&gt;
&lt;p&gt;~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args
 ~# head -20 /sys/kernel/tracing/trace
 # tracer: nop
 #
 # entries-in-buffer/entries-written: 813/26317372   #P:8
 #
 #                                _-----=&amp;gt; irqs-off/BH-disabled
 #                               / _----=&amp;gt; need-resched
 #                              | / _---=&amp;gt; hardirq/softirq
 #                              || / _--=&amp;gt; preempt-depth
 #                              ||| / _-=&amp;gt; migrate-disable
 #                              |||| /     delay
 #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
 #              | |         |   |||||     |         |
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |          fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |          tmigr_cpu_deactivate(nextexp=357988000000) {
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |            _raw_spin_lock(lock=0xf…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38327</guid>
    </item>
    <item>
      <title>GHSA-wq5h-p4xr-gc2p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wq5h-p4xr-gc2p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fgraph: Do not enable function_graph tracer when setting funcgraph-args&lt;/p&gt;
&lt;p&gt;When setting the funcgraph-args option when function graph tracer is net
enabled, it incorrectly enables it. Worse, it unregisters itself when it
was never registered. Then when it gets enabled again, it will register
itself a second time causing a WARNing.&lt;/p&gt;
&lt;p&gt;~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args
 ~# head -20 /sys/kernel/tracing/trace
 # tracer: nop
 #
 # entries-in-buffer/entries-written: 813/26317372   #P:8
 #
 #                                _-----=&amp;gt; irqs-off/BH-disabled
 #                               / _----=&amp;gt; need-resched
 #                              | / _---=&amp;gt; hardirq/softirq
 #                              || / _--=&amp;gt; preempt-depth
 #                              ||| / _-=&amp;gt; migrate-disable
 #                              |||| /     delay
 #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
 #              | |         |   |||||     |         |
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |          fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |          tmigr_cpu_deactivate(nextexp=357988000000) {
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |            _raw_spin_lock(lock=0xf…&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;fgraph: Do not enable function_graph tracer when setting funcgraph-args&lt;/p&gt;
&lt;p&gt;When setting the funcgraph-args option when function graph tracer is net
enabled, it incorrectly enables it. Worse, it unregisters itself when it
was never registered. Then when it gets enabled again, it will register
itself a second time causing a WARNing.&lt;/p&gt;
&lt;p&gt;~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args
 ~# head -20 /sys/kernel/tracing/trace
 # tracer: nop
 #
 # entries-in-buffer/entries-written: 813/26317372   #P:8
 #
 #                                _-----=&amp;gt; irqs-off/BH-disabled
 #                               / _----=&amp;gt; need-resched
 #                              | / _---=&amp;gt; hardirq/softirq
 #                              || / _--=&amp;gt; preempt-depth
 #                              ||| / _-=&amp;gt; migrate-disable
 #                              |||| /     delay
 #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
 #              | |         |   |||||     |         |
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |          fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |          tmigr_cpu_deactivate(nextexp=357988000000) {
           &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |            _raw_spin_lock(lock=0xf…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wq5h-p4xr-gc2p</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38327</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38327</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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fgraph: Do not enable function_graph tracer when setting funcgraph-args When setting the funcgraph-args option when function graph tracer is net enabled, it incorrectly enables it. Worse, it unregisters itself when it was never registered. Then when it gets enabled again, it will register itself a second time causing a WARNing.  ~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args  ~# head -20 /sys/kernel/tracing/trace  # tracer: nop  #  # entries-in-buffer/entries-written: 813/26317372   #P:8  #  #                                _-----=&amp;gt; irqs-off/BH-disabled  #                               / _----=&amp;gt; need-resched  #                              | / _---=&amp;gt; hardirq/softirq  #                              || / _--=&amp;gt; preempt-depth  #                              ||| / _-=&amp;gt; migrate-disable  #                              |||| /     delay  #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION  #              | |         |   |||||     |         |            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |      fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |      tmigr_cpu_deactivate(nextexp=357988000000) {            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |        _raw_spin_lock(lock=0xffff88823c3b2320…&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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fgraph: Do not enable function_graph tracer when setting funcgraph-args When setting the funcgraph-args option when function graph tracer is net enabled, it incorrectly enables it. Worse, it unregisters itself when it was never registered. Then when it gets enabled again, it will register itself a second time causing a WARNing.  ~# echo 1 &amp;gt; /sys/kernel/tracing/options/funcgraph-args  ~# head -20 /sys/kernel/tracing/trace  # tracer: nop  #  # entries-in-buffer/entries-written: 813/26317372   #P:8  #  #                                _-----=&amp;gt; irqs-off/BH-disabled  #                               / _----=&amp;gt; need-resched  #                              | / _---=&amp;gt; hardirq/softirq  #                              || / _--=&amp;gt; preempt-depth  #                              ||| / _-=&amp;gt; migrate-disable  #                              |||| /     delay  #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION  #              | |         |   |||||     |         |            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966010:  7)   1.692 us    |      fetch_next_timer_interrupt(basej=4294981640, basem=357956000000, base_local=0xffff88823c3ae040, base_global=0xffff88823c3af300, tevt=0xffff888100e47cb8);            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966012:  7)               |      tmigr_cpu_deactivate(nextexp=357988000000) {            &amp;lt;idle&amp;gt;-0       [007] d..4.   358.966013:  7)               |        _raw_spin_lock(lock=0xffff88823c3b2320…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38327</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1522 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1522</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1522</guid>
    </item>
  </channel>
</rss>
