<?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://db.gcve.eu</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, 19 Nov 2026 17:55:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21681 — openvswitch: fix lockup on tx to unregistering netdev with carrier</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21681</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;openvswitch: fix lockup on tx to unregistering netdev with carrier&lt;/p&gt;
&lt;p&gt;Commit in a fixes tag attempted to fix the issue in the following
sequence of calls:&lt;/p&gt;
&lt;p&gt;do_output
    -&amp;gt; ovs_vport_send
       -&amp;gt; dev_queue_xmit
          -&amp;gt; __dev_queue_xmit
             -&amp;gt; netdev_core_pick_tx
                -&amp;gt; skb_tx_hash&lt;/p&gt;
&lt;p&gt;When device is unregistering, the &amp;#39;dev-&amp;gt;real_num_tx_queues&amp;#39; goes to
zero and the &amp;#39;while (unlikely(hash &amp;gt;= qcount))&amp;#39; loop inside the
&amp;#39;skb_tx_hash&amp;#39; becomes infinite, locking up the core forever.&lt;/p&gt;
&lt;p&gt;But unfortunately, checking just the carrier status is not enough to
fix the issue, because some devices may still be in unregistering
state while reporting carrier status OK.&lt;/p&gt;
&lt;p&gt;One example of such device is a net/dummy.  It sets carrier ON
on start, but it doesn&amp;#39;t implement .ndo_stop to set the carrier off.
And it makes sense, because dummy doesn&amp;#39;t really have a carrier.
Therefore, while this device is unregistering, it&amp;#39;s still easy to hit
the infinite loop in the skb_tx_hash() from the OVS datapath.  There
might be other drivers that do the same, but dummy by itself is
important for the OVS ecosystem, because it is frequently used as a
packet sink for tcpdump while debugging OVS deployments.  And when the
issue is hit, the only way to recover is to reboot.&lt;/p&gt;
&lt;p&gt;Fix that by also checking if the device is running.  The running
state is handled by the net core during unregistering, so it covers
unregistering case be…&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;openvswitch: fix lockup on tx to unregistering netdev with carrier&lt;/p&gt;
&lt;p&gt;Commit in a fixes tag attempted to fix the issue in the following
sequence of calls:&lt;/p&gt;
&lt;p&gt;do_output
    -&amp;gt; ovs_vport_send
       -&amp;gt; dev_queue_xmit
          -&amp;gt; __dev_queue_xmit
             -&amp;gt; netdev_core_pick_tx
                -&amp;gt; skb_tx_hash&lt;/p&gt;
&lt;p&gt;When device is unregistering, the &amp;#39;dev-&amp;gt;real_num_tx_queues&amp;#39; goes to
zero and the &amp;#39;while (unlikely(hash &amp;gt;= qcount))&amp;#39; loop inside the
&amp;#39;skb_tx_hash&amp;#39; becomes infinite, locking up the core forever.&lt;/p&gt;
&lt;p&gt;But unfortunately, checking just the carrier status is not enough to
fix the issue, because some devices may still be in unregistering
state while reporting carrier status OK.&lt;/p&gt;
&lt;p&gt;One example of such device is a net/dummy.  It sets carrier ON
on start, but it doesn&amp;#39;t implement .ndo_stop to set the carrier off.
And it makes sense, because dummy doesn&amp;#39;t really have a carrier.
Therefore, while this device is unregistering, it&amp;#39;s still easy to hit
the infinite loop in the skb_tx_hash() from the OVS datapath.  There
might be other drivers that do the same, but dummy by itself is
important for the OVS ecosystem, because it is frequently used as a
packet sink for tcpdump while debugging OVS deployments.  And when the
issue is hit, the only way to recover is to reboot.&lt;/p&gt;
&lt;p&gt;Fix that by also checking if the device is running.  The running
state is handled by the net core during unregistering, so it covers
unregistering case be…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21681</guid>
    </item>
    <item>
      <title>USN-7445-1 — linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle,…</title>
      <link>https://db.gcve.eu/vuln/usn-7445-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7445-1</guid>
    </item>
  </channel>
</rss>
