<?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, 02 Oct 2026 22:09:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53008</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53008</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53008</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-329931</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329931</link>
      <description>EUVD-2026-329931</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329931</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53008</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53008</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix race condition in TX timestamp ring cleanup&lt;/p&gt;
&lt;p&gt;Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map()
that can cause a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag
after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map
call on another CPU to dereference the tstamp_ring, which could lead to
a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()
  --------------------------------|---------------------------------
  tx_ring-&amp;gt;tstamp_ring = NULL     |
                                  | ice_is_txtime_cfg() -&amp;gt; true
                                  | tstamp_ring = tx_ring-&amp;gt;tstamp_ring
                                  | tstamp_ring-&amp;gt;count  // NULL deref!
  flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   |&lt;/p&gt;
&lt;p&gt;Fix by:
1. Reordering ice_free_tx_tstamp_ring() to clear the flag before
   NULLing the pointer, with smp_wmb() to ensure proper ordering.
2. Adding smp_rmb() in ice_tx_map() after the flag check to order the
   flag read before the pointer read, using READ_ONCE() for the
   pointer, and adding a NULL check as a safety net.
3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using
   atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag
   operations throughout the driver:
   - ICE_TX_RING_FLAGS_XDP
   - ICE_TX_RING_FLAGS_VLAN_L2TAG1
   - ICE_TX_RING_FLAGS_VLAN_L2TAG2
   - ICE_TX_RING_FLA…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix race condition in TX timestamp ring cleanup&lt;/p&gt;
&lt;p&gt;Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map()
that can cause a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag
after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map
call on another CPU to dereference the tstamp_ring, which could lead to
a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()
  --------------------------------|---------------------------------
  tx_ring-&amp;gt;tstamp_ring = NULL     |
                                  | ice_is_txtime_cfg() -&amp;gt; true
                                  | tstamp_ring = tx_ring-&amp;gt;tstamp_ring
                                  | tstamp_ring-&amp;gt;count  // NULL deref!
  flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   |&lt;/p&gt;
&lt;p&gt;Fix by:
1. Reordering ice_free_tx_tstamp_ring() to clear the flag before
   NULLing the pointer, with smp_wmb() to ensure proper ordering.
2. Adding smp_rmb() in ice_tx_map() after the flag check to order the
   flag read before the pointer read, using READ_ONCE() for the
   pointer, and adding a NULL check as a safety net.
3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using
   atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag
   operations throughout the driver:
   - ICE_TX_RING_FLAGS_XDP
   - ICE_TX_RING_FLAGS_VLAN_L2TAG1
   - ICE_TX_RING_FLAGS_VLAN_L2TAG2
   - ICE_TX_RING_FLA…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53008</guid>
    </item>
    <item>
      <title>GHSA-gqxp-fj3h-cr3v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gqxp-fj3h-cr3v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix race condition in TX timestamp ring cleanup&lt;/p&gt;
&lt;p&gt;Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map()
that can cause a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag
after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map
call on another CPU to dereference the tstamp_ring, which could lead to
a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()
  --------------------------------|---------------------------------
  tx_ring-&amp;gt;tstamp_ring = NULL     |
                                  | ice_is_txtime_cfg() -&amp;gt; true
                                  | tstamp_ring = tx_ring-&amp;gt;tstamp_ring
                                  | tstamp_ring-&amp;gt;count  // NULL deref!
  flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   |&lt;/p&gt;
&lt;p&gt;Fix by:
1. Reordering ice_free_tx_tstamp_ring() to clear the flag before
   NULLing the pointer, with smp_wmb() to ensure proper ordering.
2. Adding smp_rmb() in ice_tx_map() after the flag check to order the
   flag read before the pointer read, using READ_ONCE() for the
   pointer, and adding a NULL check as a safety net.
3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using
   atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag
   operations throughout the driver:
   - ICE_TX_RING_FLAGS_XDP
   - ICE_TX_RING_FLAGS_VLAN_L2TAG1
   - ICE_TX_RING_FLAGS_VLAN_L2TAG2
   - ICE_TX_RING_FLA…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix race condition in TX timestamp ring cleanup&lt;/p&gt;
&lt;p&gt;Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map()
that can cause a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag
after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map
call on another CPU to dereference the tstamp_ring, which could lead to
a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()
  --------------------------------|---------------------------------
  tx_ring-&amp;gt;tstamp_ring = NULL     |
                                  | ice_is_txtime_cfg() -&amp;gt; true
                                  | tstamp_ring = tx_ring-&amp;gt;tstamp_ring
                                  | tstamp_ring-&amp;gt;count  // NULL deref!
  flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   |&lt;/p&gt;
&lt;p&gt;Fix by:
1. Reordering ice_free_tx_tstamp_ring() to clear the flag before
   NULLing the pointer, with smp_wmb() to ensure proper ordering.
2. Adding smp_rmb() in ice_tx_map() after the flag check to order the
   flag read before the pointer read, using READ_ONCE() for the
   pointer, and adding a NULL check as a safety net.
3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using
   atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag
   operations throughout the driver:
   - ICE_TX_RING_FLAGS_XDP
   - ICE_TX_RING_FLAGS_VLAN_L2TAG1
   - ICE_TX_RING_FLAGS_VLAN_L2TAG2
   - ICE_TX_RING_FLA…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gqxp-fj3h-cr3v</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53008</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53008</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix race condition in TX timestamp ring cleanup Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointer dereference. ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map call on another CPU to dereference the tstamp_ring, which could lead to a NULL pointer dereference.   CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()   --------------------------------|---------------------------------   tx_ring-&amp;gt;tstamp_ring = NULL     |                                   | ice_is_txtime_cfg() -&amp;gt; true                                   | tstamp_ring = tx_ring-&amp;gt;tstamp_ring                                   | tstamp_ring-&amp;gt;count  // NULL deref!   flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   | Fix by: 1. Reordering ice_free_tx_tstamp_ring() to clear the flag before    NULLing the pointer, with smp_wmb() to ensure proper ordering. 2. Adding smp_rmb() in ice_tx_map() after the flag check to order the    flag read before the pointer read, using READ_ONCE() for the    pointer, and adding a NULL check as a safety net. 3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using    atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag    operations throughout the driver:    - ICE_TX_RING_FLAGS_XDP    - ICE_TX_RING_FLAGS_VLAN_L2TAG1    - ICE_TX_RING_FLAGS_VLAN_L2TAG2    - ICE_TX_RING_FLAGS_TX…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix race condition in TX timestamp ring cleanup Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointer dereference. ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map call on another CPU to dereference the tstamp_ring, which could lead to a NULL pointer dereference.   CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()   --------------------------------|---------------------------------   tx_ring-&amp;gt;tstamp_ring = NULL     |                                   | ice_is_txtime_cfg() -&amp;gt; true                                   | tstamp_ring = tx_ring-&amp;gt;tstamp_ring                                   | tstamp_ring-&amp;gt;count  // NULL deref!   flags &amp;amp;= ~ICE_TX_FLAGS_TXTIME   | Fix by: 1. Reordering ice_free_tx_tstamp_ring() to clear the flag before    NULLing the pointer, with smp_wmb() to ensure proper ordering. 2. Adding smp_rmb() in ice_tx_map() after the flag check to order the    flag read before the pointer read, using READ_ONCE() for the    pointer, and adding a NULL check as a safety net. 3. Converting tx_ring-&amp;gt;flags from u8 to DECLARE_BITMAP() and using    atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag    operations throughout the driver:    - ICE_TX_RING_FLAGS_XDP    - ICE_TX_RING_FLAGS_VLAN_L2TAG1    - ICE_TX_RING_FLAGS_VLAN_L2TAG2    - ICE_TX_RING_FLAGS_TX…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53008</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
