CVE-2025-71079

Description

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.

Gravité et risque d'exploitation

CVE-2025-71079 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.11 %, ce qui la place devant 1.1 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012, 6.12.64, <=6.1.*, <=6.12.*, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 5.16, 6.1.160, 0, 6.6.120, <4.10, <5.15.198, 5.15.198, 4.14.256, <4.20, <=5.10.*, <=6.6.*, 47244ac0b65bd74cc70007d8e1bac68bd2baad19, 4.9.291, 6.18.4, 5.4.162, 5.10.82, <5.10.248, 73a0d12114b4bc1a9def79a623264754b9df698e, 5ef16d2d172ee56714cff37cd005b98aba08ef5a, <4.5, 5.15.5, <5.5, 8a9c61c3ef187d8891225f9b932390670a43a0d3, <5.16, <6b93c8ab6f6cda8818983a4ae3fcf84b023037b4, <8fc4632fb508432895430cd02b38086bdd649083, <=6.18.*, <ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5, 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6, <f3a8a7c1aa278f2378b2f3a10500c6674dffdfda, c45cea83e13699bdfd47842e04d09dd43af4c371, 5.10.248, 4.19.218, <=*, <2e0831e9fc46a06daa6d4d8d57a2738e343130c3, ff169909eac9e00bf1aa0af739ba6ddfb1b1d135, <=5.15.*, 6.19, <1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5, 4.4.293, <4.15) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/2e0831e9fc46a06daa6d4d8d57a2738e343130c3
• https://git.kernel.org/stable/c/e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012
• https://git.kernel.org/stable/c/ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5
• https://git.kernel.org/stable/c/6b93c8ab6f6cda8818983a4ae3fcf84b023037b4
• https://git.kernel.org/stable/c/8fc4632fb508432895430cd02b38086bdd649083
• https://git.kernel.org/stable/c/f3a8a7c1aa278f2378b2f3a10500c6674dffdfda
• https://git.kernel.org/stable/c/1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5