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

Katalog CVE

CVSS 5.5 · Medium EPSS 0,10%

Kerentanan Improper Locking pada linux kernel. Skor CVSS 3.1 5.5 (Medium) menurut NVD.

Deskripsi (NVD)

In the Linux kernel, the following vulnerability has been resolved: net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write A deadlock can occur between nfc_unregister_device() and rfkill_fop_write() due to lock ordering inversion between device_lock and rfkill_global_mutex. The problematic lock order is: Thread A (rfkill_fop_write): rfkill_fop_write() mutex_lock(&rfkill_global_mutex) rfkill_set_block() nfc_rfkill_set_block() nfc_dev_down() device_lock(&dev->dev) <- waits for device_lock Thread B (nfc_unregister_device): nfc_unregister_device() device_lock(&dev->dev) rfkill_unregister() mutex_lock(&rfkill_global_mutex) <- waits for rfkill_global_mutex This creates a classic ABBA deadlock scenario. Fix this by moving rfkill_unregister() and rfkill_destroy() outside the device_lock critical section. Store the rfkill pointer in a local variable before releasing the lock, then call rfkill_unregister() after releasing device_lock. This change is safe because rfkill_fop_write() holds rfkill_global_mutex while calling the rfkill callbacks, and rfkill_unregister() also acquires rfkill_global_mutex before cleanup. Therefore, rfkill_unregister() will wait for any ongoing callback to complete before proceeding, and device_del() is only called after rfkill_unregister() returns, preventing any use-after-free. The similar lock ordering in nfc_register_device() (device_lock -> rfkill_global_mutex via rfkill_register) is safe because during registration the device is not yet in rfkill_list, so no concurrent rfkill operations can occur on this device.

Rincian

Terbit di NVD
13 Januari 2026
Terakhir diubah
14 Juli 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-667: Improper Locking
EPSS (30 hari)
0,10% peluang dieksploitasi; lebih tinggi dari 0,9% CVE lain

Produk dan versi terdampak

VendorProdukVersi terdampak
linux linux kernel Versi 4.4.293 hingga sebelum 4.5
linux linux kernel Versi 4.9.291 hingga sebelum 4.10
linux linux kernel Versi 4.14.256 hingga sebelum 4.15
linux linux kernel Versi 4.19.218 hingga sebelum 4.20
linux linux kernel Versi 5.4.162 hingga sebelum 5.5
linux linux kernel Versi 5.10.82 hingga sebelum 5.10.248
linux linux kernel Versi 5.15.5 hingga sebelum 5.15.198
linux linux kernel Versi 5.16.1 hingga sebelum 6.1.160
linux linux kernel Versi 6.2 hingga sebelum 6.6.120
linux linux kernel Versi 6.7 hingga sebelum 6.12.64
linux linux kernel Versi 6.13 hingga sebelum 6.18.4
linux linux kernel Versi 5.16
linux linux kernel Versi 6.19 rc1
linux linux kernel Versi 6.19 rc2
linux linux kernel Versi 6.19 rc3
linux linux kernel Versi 6.19 rc4
linux linux kernel Versi 6.19 rc5
linux linux kernel Versi 6.19 rc6
linux linux kernel Versi 6.19 rc7
linux linux kernel Versi 6.19 rc8

> 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.