csirt@kutim:~/threat-intel/cve/CVE-2025-21681

Katalog CVE

CVSS 5.5 · Medium EPSS 0,22%

Kerentanan Loop with Unreachable Exit Condition ('Infinite Loop') pada linux kernel. Skor CVSS 3.1 5.5 (Medium) menurut NVD.

Deskripsi (NVD)

In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix lockup on tx to unregistering netdev with carrier Commit in a fixes tag attempted to fix the issue in the following sequence of calls: do_output -> ovs_vport_send -> dev_queue_xmit -> __dev_queue_xmit -> netdev_core_pick_tx -> skb_tx_hash When device is unregistering, the 'dev->real_num_tx_queues' goes to zero and the 'while (unlikely(hash >= qcount))' loop inside the 'skb_tx_hash' becomes infinite, locking up the core forever. 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. One example of such device is a net/dummy. It sets carrier ON on start, but it doesn't implement .ndo_stop to set the carrier off. And it makes sense, because dummy doesn't really have a carrier. Therefore, while this device is unregistering, it'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. 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 better, and we don't really need to send packets to devices that are not running anyway. While only checking the running state might be enough, the carrier check is preserved. The running and the carrier states seem disjoined throughout the code and different drivers. And other core functions like __dev_direct_xmit() check both before attempting to transmit a packet. So, it seems safer to check both flags in OVS as well.

Rincian

Terbit di NVD
31 Januari 2025
Terakhir diubah
17 Juni 2026
Status NVD
Modified
CVSS 3.1
5.5 (Medium), sumber NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H · uraikan di kalkulator
Jenis kelemahan (CWE)
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
EPSS (30 hari)
0,22% peluang dieksploitasi; lebih tinggi dari 11,1% CVE lain

Produk dan versi terdampak

VendorProdukVersi terdampak
linux linux kernel Versi 6.1.25 hingga sebelum 6.1.127
linux linux kernel Versi 6.2.12 hingga sebelum 6.6.74
linux linux kernel Versi 6.7 hingga sebelum 6.12.11
linux linux kernel Versi 6.13 rc1
linux linux kernel Versi 6.13 rc2
linux linux kernel Versi 6.13 rc3
linux linux kernel Versi 6.13 rc4
linux linux kernel Versi 6.13 rc5
linux linux kernel Versi 6.13 rc6
linux linux kernel Versi 6.13 rc7

> Data dari konfigurasi CPE di NVD.

Referensi dan perbaikan

Sumber: NVD · CVE.org · EPSS. Halaman ini disusun otomatis dari data tersebut; pembaruan terakhir 5 Okt 2026, 20:11 WITA. Kalau sistem di Perangkat Daerah memakai produk ini dan butuh bantuan, laporkan lewat kanal pelaporan.