<?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, 15 Oct 2026 12:42:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39813 — ftrace: Fix potential warning in trace_printk_seq during ftrace_dump</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-39813</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ftrace: Fix potential warning in trace_printk_seq during ftrace_dump&lt;/p&gt;
&lt;p&gt;When calling ftrace_dump_one() concurrently with reading trace_pipe,
a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race
condition.&lt;/p&gt;
&lt;p&gt;The issue occurs because:&lt;/p&gt;
&lt;p&gt;CPU0 (ftrace_dump)                              CPU1 (reader)
echo z &amp;gt; /proc/sysrq-trigger&lt;/p&gt;
&lt;p&gt;!trace_empty(&amp;amp;iter)
trace_iterator_reset(&amp;amp;iter) &amp;lt;- len = size = 0
                                                cat /sys/kernel/tracing/trace_pipe
trace_find_next_entry_inc(&amp;amp;iter)
  __find_next_entry
    ring_buffer_empty_cpu &amp;lt;- all empty
  return NULL&lt;/p&gt;
&lt;p&gt;trace_printk_seq(&amp;amp;iter.seq)
  WARN_ON_ONCE(s-&amp;gt;seq.len &amp;gt;= s-&amp;gt;seq.size)&lt;/p&gt;
&lt;p&gt;In the context between trace_empty() and trace_find_next_entry_inc()
during ftrace_dump, the ring buffer data was consumed by other readers.
This caused trace_find_next_entry_inc to return NULL, failing to populate
`iter.seq`. At this point, due to the prior trace_iterator_reset, both
`iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal,
the WARN_ON_ONCE condition is triggered.&lt;/p&gt;
&lt;p&gt;Move the trace_printk_seq() into the if block that checks to make sure the
return value of trace_find_next_entry_inc() is non-NULL in
ftrace_dump_one(), ensuring the &amp;#39;iter.seq&amp;#39; is properly populated before
subsequent operations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ftrace: Fix potential warning in trace_printk_seq during ftrace_dump&lt;/p&gt;
&lt;p&gt;When calling ftrace_dump_one() concurrently with reading trace_pipe,
a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race
condition.&lt;/p&gt;
&lt;p&gt;The issue occurs because:&lt;/p&gt;
&lt;p&gt;CPU0 (ftrace_dump)                              CPU1 (reader)
echo z &amp;gt; /proc/sysrq-trigger&lt;/p&gt;
&lt;p&gt;!trace_empty(&amp;amp;iter)
trace_iterator_reset(&amp;amp;iter) &amp;lt;- len = size = 0
                                                cat /sys/kernel/tracing/trace_pipe
trace_find_next_entry_inc(&amp;amp;iter)
  __find_next_entry
    ring_buffer_empty_cpu &amp;lt;- all empty
  return NULL&lt;/p&gt;
&lt;p&gt;trace_printk_seq(&amp;amp;iter.seq)
  WARN_ON_ONCE(s-&amp;gt;seq.len &amp;gt;= s-&amp;gt;seq.size)&lt;/p&gt;
&lt;p&gt;In the context between trace_empty() and trace_find_next_entry_inc()
during ftrace_dump, the ring buffer data was consumed by other readers.
This caused trace_find_next_entry_inc to return NULL, failing to populate
`iter.seq`. At this point, due to the prior trace_iterator_reset, both
`iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal,
the WARN_ON_ONCE condition is triggered.&lt;/p&gt;
&lt;p&gt;Move the trace_printk_seq() into the if block that checks to make sure the
return value of trace_find_next_entry_inc() is non-NULL in
ftrace_dump_one(), ensuring the &amp;#39;iter.seq&amp;#39; is properly populated before
subsequent operations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-39813</guid>
    </item>
    <item>
      <title>USN-7909-1 — linux, linux-aws, linux-aws-5.15, linux-gcp-5.15, linux-hwe-5.15, linux-ibm, linux-ibm-5.15, linux-intel-iotg, linux-in…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7909-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws and 8 more&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - ATM drivers;
  - DRBD Distributed Replicated Block Device drivers;
  - Bus devices;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PCCARD (PCMCIA/CardBus) bus subsystem;
  - PHY drivers;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - ASPEED SoC drivers;
  - QCOM SoC drivers;
  - small TFT LCD display modules;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - Framebuffer layer;
  - BTRFS file system;
  - File systems infrastructure;
  - EF…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws and 8 more&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - ATM drivers;
  - DRBD Distributed Replicated Block Device drivers;
  - Bus devices;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PCCARD (PCMCIA/CardBus) bus subsystem;
  - PHY drivers;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - ASPEED SoC drivers;
  - QCOM SoC drivers;
  - small TFT LCD display modules;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - Framebuffer layer;
  - BTRFS file system;
  - File systems infrastructure;
  - EF…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7909-1</guid>
    </item>
  </channel>
</rss>
