<?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>Fri, 16 Oct 2026 20:17:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37920 — xsk: Fix race condition in AF_XDP generic RX path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-37920</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;xsk: Fix race condition in AF_XDP generic RX path&lt;/p&gt;
&lt;p&gt;Move rx_lock from xsk_socket to xsk_buff_pool.
Fix synchronization for shared umem mode in
generic RX path where multiple sockets share
single xsk_buff_pool.&lt;/p&gt;
&lt;p&gt;RX queue is exclusive to xsk_socket, while FILL
queue can be shared between multiple sockets.
This could result in race condition where two
CPU cores access RX path of two different sockets
sharing the same umem.&lt;/p&gt;
&lt;p&gt;Protect both queues by acquiring spinlock in shared
xsk_buff_pool.&lt;/p&gt;
&lt;p&gt;Lock contention may be minimized in the future by some
per-thread FQ buffering.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s safe and necessary to move spin_lock_bh(rx_lock)
after xsk_rcv_check():
* xs-&amp;gt;pool and spinlock_init is synchronized by
  xsk_bind() -&amp;gt; xsk_is_bound() memory barriers.
* xsk_rcv_check() may return true at the moment
  of xsk_release() or xsk_unbind_dev(),
  however this will not cause any data races or
  race conditions. xsk_unbind_dev() removes xdp
  socket from all maps and waits for completion
  of all outstanding rx operations. Packets in
  RX path will either complete safely or drop.&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;xsk: Fix race condition in AF_XDP generic RX path&lt;/p&gt;
&lt;p&gt;Move rx_lock from xsk_socket to xsk_buff_pool.
Fix synchronization for shared umem mode in
generic RX path where multiple sockets share
single xsk_buff_pool.&lt;/p&gt;
&lt;p&gt;RX queue is exclusive to xsk_socket, while FILL
queue can be shared between multiple sockets.
This could result in race condition where two
CPU cores access RX path of two different sockets
sharing the same umem.&lt;/p&gt;
&lt;p&gt;Protect both queues by acquiring spinlock in shared
xsk_buff_pool.&lt;/p&gt;
&lt;p&gt;Lock contention may be minimized in the future by some
per-thread FQ buffering.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s safe and necessary to move spin_lock_bh(rx_lock)
after xsk_rcv_check():
* xs-&amp;gt;pool and spinlock_init is synchronized by
  xsk_bind() -&amp;gt; xsk_is_bound() memory barriers.
* xsk_rcv_check() may return true at the moment
  of xsk_release() or xsk_unbind_dev(),
  however this will not cause any data races or
  race conditions. xsk_unbind_dev() removes xdp
  socket from all maps and waits for completion
  of all outstanding rx operations. Packets in
  RX path will either complete safely or drop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-37920</guid>
    </item>
    <item>
      <title>USN-7649-1 — linux, linux-gcp, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7649-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&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;
  - PA-RISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - ARM SCMI message protocol;
  - GPU drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Multiple devices driver;
  - Network drivers;
  - PCI subsystem;
  - PTP clock framework;
  - SPI subsystem;
  - BTRFS file system;
  - SMB network file system;
  - eXpress Data Path;
  - Universal MIDI packet (UMP) support module;
  - Tracing infrastructure;
  - Memory management;
  - IPv4 networking;
  - IPv6 networking;
  - Network traffic control;
  - AMD SoC Alsa drivers;
  - SoC Audio generic drivers;
(CVE-2025-37898, CVE-2025-37990, CVE-2025-37974, CVE-2025-37991,
CVE-2025-37894, CVE-2025-37906, CVE-2025-37896, CVE-2025-37909,
CVE-2025-37923, CVE-2025-37899, CVE-2025-37901, CVE-2025-37914,
CVE-2025-38216, CVE-2025-37931, CVE-2025-37928, CVE-2025-37916,
CVE-2025-37908, CVE-2025-37915, CVE-2025-37917, CVE-2025-37921,
CVE-2025-37903, CVE-2025-37922, CVE-2025-37895, CVE-2025-37936,
CVE-2025-37933, CVE-2025-37891, CVE-2025-37926, CVE-2025-37912,
CVE-2025-37920, CVE-2025-37924, CVE-2025-37927, CVE-2025-37946,
CVE-2025-37907, CVE-2025-37930, CVE-2025-37911, CVE-2025-37905,
CVE-2025-37900, CVE-202…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&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;
  - PA-RISC architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - ARM SCMI message protocol;
  - GPU drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Multiple devices driver;
  - Network drivers;
  - PCI subsystem;
  - PTP clock framework;
  - SPI subsystem;
  - BTRFS file system;
  - SMB network file system;
  - eXpress Data Path;
  - Universal MIDI packet (UMP) support module;
  - Tracing infrastructure;
  - Memory management;
  - IPv4 networking;
  - IPv6 networking;
  - Network traffic control;
  - AMD SoC Alsa drivers;
  - SoC Audio generic drivers;
(CVE-2025-37898, CVE-2025-37990, CVE-2025-37974, CVE-2025-37991,
CVE-2025-37894, CVE-2025-37906, CVE-2025-37896, CVE-2025-37909,
CVE-2025-37923, CVE-2025-37899, CVE-2025-37901, CVE-2025-37914,
CVE-2025-38216, CVE-2025-37931, CVE-2025-37928, CVE-2025-37916,
CVE-2025-37908, CVE-2025-37915, CVE-2025-37917, CVE-2025-37921,
CVE-2025-37903, CVE-2025-37922, CVE-2025-37895, CVE-2025-37936,
CVE-2025-37933, CVE-2025-37891, CVE-2025-37926, CVE-2025-37912,
CVE-2025-37920, CVE-2025-37924, CVE-2025-37927, CVE-2025-37946,
CVE-2025-37907, CVE-2025-37930, CVE-2025-37911, CVE-2025-37905,
CVE-2025-37900, CVE-202…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7649-1</guid>
    </item>
  </channel>
</rss>
