<?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 06:24:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23103 — ipvlan: Make the addrs_lock be per port</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-23103</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, 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;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, 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;ipvlan: Make the addrs_lock be per port&lt;/p&gt;
&lt;p&gt;Make the addrs_lock be per port, not per ipvlan dev.&lt;/p&gt;
&lt;p&gt;Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So&lt;/p&gt;
&lt;p&gt;1) Introduce per-port addrs_lock.&lt;/p&gt;
&lt;p&gt;2) It was needed to fix places where it was forgotten
to take lock (ipvlan_open/ipvlan_close)&lt;/p&gt;
&lt;p&gt;This appears to be a very minor problem though.
Since it&amp;#39;s highly unlikely that ipvlan_add_addr() will
be called on 2 CPU simultaneously. But nevertheless,
this could cause:&lt;/p&gt;
&lt;p&gt;1) False-negative of ipvlan_addr_busy(): one interface
iterated through all port-&amp;gt;ipvlans + ipvlan-&amp;gt;addrs
under some ipvlan spinlock, and another added IP
under its own lock. Though this is only possible
for IPv6, since looks like only ipvlan_addr6_event() can be
called without rtnl_lock.&lt;/p&gt;
&lt;p&gt;2) Race since ipvlan_ht_addr_add(port) is called under
different ipvlan-&amp;gt;addrs_lock locks&lt;/p&gt;
&lt;p&gt;This should not affect performance, since add/remove IP
is a rare situation and spinlock is not taken on fast
paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-23103</guid>
    </item>
    <item>
      <title>USN-8162-1 — linux-nvidia-tegra-5.15 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8162-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&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:
  - ARM64 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&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:
  - ARM64 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8162-1</guid>
    </item>
  </channel>
</rss>
