<?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, 10 Oct 2026 11:27:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21986 — net: switchdev: Convert blocking notification chain to a raw one</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-21986</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: switchdev: Convert blocking notification chain to a raw one&lt;/p&gt;
&lt;p&gt;A blocking notification chain uses a read-write semaphore to protect the
integrity of the chain. The semaphore is acquired for writing when
adding / removing notifiers to / from the chain and acquired for reading
when traversing the chain and informing notifiers about an event.&lt;/p&gt;
&lt;p&gt;In case of the blocking switchdev notification chain, recursive
notifications are possible which leads to the semaphore being acquired
twice for reading and to lockdep warnings being generated [1].&lt;/p&gt;
&lt;p&gt;Specifically, this can happen when the bridge driver processes a
SWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications
about deferred events when calling switchdev_deferred_process().&lt;/p&gt;
&lt;p&gt;Fix this by converting the notification chain to a raw notification
chain in a similar fashion to the netdev notification chain. Protect
the chain using the RTNL mutex by acquiring it when modifying the chain.
Events are always informed under the RTNL mutex, but add an assertion in
call_switchdev_blocking_notifiers() to make sure this is not violated in
the future.&lt;/p&gt;
&lt;p&gt;Maintain the &amp;#34;blocking&amp;#34; prefix as events are always emitted from process
context and listeners are allowed to block.&lt;/p&gt;
&lt;p&gt;[1]:
WARNING: possible recursive locking detected
6.14.0-rc4-custom-g079270089484 #1 Not tainted
--------------------------------------------
ip/52731 is trying to acquire lock:
ffffffff850918d8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: switchdev: Convert blocking notification chain to a raw one&lt;/p&gt;
&lt;p&gt;A blocking notification chain uses a read-write semaphore to protect the
integrity of the chain. The semaphore is acquired for writing when
adding / removing notifiers to / from the chain and acquired for reading
when traversing the chain and informing notifiers about an event.&lt;/p&gt;
&lt;p&gt;In case of the blocking switchdev notification chain, recursive
notifications are possible which leads to the semaphore being acquired
twice for reading and to lockdep warnings being generated [1].&lt;/p&gt;
&lt;p&gt;Specifically, this can happen when the bridge driver processes a
SWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications
about deferred events when calling switchdev_deferred_process().&lt;/p&gt;
&lt;p&gt;Fix this by converting the notification chain to a raw notification
chain in a similar fashion to the netdev notification chain. Protect
the chain using the RTNL mutex by acquiring it when modifying the chain.
Events are always informed under the RTNL mutex, but add an assertion in
call_switchdev_blocking_notifiers() to make sure this is not violated in
the future.&lt;/p&gt;
&lt;p&gt;Maintain the &amp;#34;blocking&amp;#34; prefix as events are always emitted from process
context and listeners are allowed to block.&lt;/p&gt;
&lt;p&gt;[1]:
WARNING: possible recursive locking detected
6.14.0-rc4-custom-g079270089484 #1 Not tainted
--------------------------------------------
ip/52731 is trying to acquire lock:
ffffffff850918d8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-21986</guid>
    </item>
    <item>
      <title>USN-7605-1 — linux, linux-aws, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7605-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&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;
  - PowerPC architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bus devices;
  - AMD CDX bus driver;
  - Clock framework and drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - VideoCore services drivers;
  - Thermal drivers;
  - USB DSL drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Virtio Host (VHOST) subsystem;
  - Fr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&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;
  - PowerPC architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bus devices;
  - AMD CDX bus driver;
  - Clock framework and drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - VideoCore services drivers;
  - Thermal drivers;
  - USB DSL drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Virtio Host (VHOST) subsystem;
  - Fr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7605-1</guid>
    </item>
  </channel>
</rss>
