<?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:28:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38614 — eventpoll: Fix semi-unbounded recursion</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38614</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eventpoll: Fix semi-unbounded recursion&lt;/p&gt;
&lt;p&gt;Ensure that epoll instances can never form a graph deeper than
EP_MAX_NESTS+1 links.&lt;/p&gt;
&lt;p&gt;Currently, ep_loop_check_proc() ensures that the graph is loop-free and
does some recursion depth checks, but those recursion depth checks don&amp;#39;t
limit the depth of the resulting tree for two reasons:&lt;/p&gt;
&lt;p&gt;- They don&amp;#39;t look upwards in the tree.
 - If there are multiple downwards paths of different lengths, only one of
   the paths is actually considered for the depth check since commit
   28d82dc1c4ed (&amp;#34;epoll: limit paths&amp;#34;).&lt;/p&gt;
&lt;p&gt;Essentially, the current recursion depth check in ep_loop_check_proc() just
serves to prevent it from recursing too deeply while checking for loops.&lt;/p&gt;
&lt;p&gt;A more thorough check is done in reverse_path_check() after the new graph
edge has already been created; this checks, among other things, that no
paths going upwards from any non-epoll file with a length of more than 5
edges exist. However, this check does not apply to non-epoll files.&lt;/p&gt;
&lt;p&gt;As a result, it is possible to recurse to a depth of at least roughly 500,
tested on v6.15. (I am unsure if deeper recursion is possible; and this may
have changed with commit 8c44dac8add7 (&amp;#34;eventpoll: Fix priority inversion
problem&amp;#34;).)&lt;/p&gt;
&lt;p&gt;To fix it:&lt;/p&gt;
&lt;p&gt;1. In ep_loop_check_proc(), note the subtree depth of each visited node,
and use subtree depths for the total depth calculation even when a subtree
has already been visited.
2. Add ep_get_u…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eventpoll: Fix semi-unbounded recursion&lt;/p&gt;
&lt;p&gt;Ensure that epoll instances can never form a graph deeper than
EP_MAX_NESTS+1 links.&lt;/p&gt;
&lt;p&gt;Currently, ep_loop_check_proc() ensures that the graph is loop-free and
does some recursion depth checks, but those recursion depth checks don&amp;#39;t
limit the depth of the resulting tree for two reasons:&lt;/p&gt;
&lt;p&gt;- They don&amp;#39;t look upwards in the tree.
 - If there are multiple downwards paths of different lengths, only one of
   the paths is actually considered for the depth check since commit
   28d82dc1c4ed (&amp;#34;epoll: limit paths&amp;#34;).&lt;/p&gt;
&lt;p&gt;Essentially, the current recursion depth check in ep_loop_check_proc() just
serves to prevent it from recursing too deeply while checking for loops.&lt;/p&gt;
&lt;p&gt;A more thorough check is done in reverse_path_check() after the new graph
edge has already been created; this checks, among other things, that no
paths going upwards from any non-epoll file with a length of more than 5
edges exist. However, this check does not apply to non-epoll files.&lt;/p&gt;
&lt;p&gt;As a result, it is possible to recurse to a depth of at least roughly 500,
tested on v6.15. (I am unsure if deeper recursion is possible; and this may
have changed with commit 8c44dac8add7 (&amp;#34;eventpoll: Fix priority inversion
problem&amp;#34;).)&lt;/p&gt;
&lt;p&gt;To fix it:&lt;/p&gt;
&lt;p&gt;1. In ep_loop_check_proc(), note the subtree depth of each visited node,
and use subtree depths for the total depth calculation even when a subtree
has already been visited.
2. Add ep_get_u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38614</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>
