CVE-2025-71079 - CVE House
Back to Database
Status published Unknown CVE-2025-71079

net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write

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

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2025-71079

Credits & Attribution

No credits recorded in the NVD database.

References

More from Linux

View All →
CVE-2025-71315
drm/vkms: Convert to DRM's vblank timer
Unknown 0
CVE-2025-71314
drm/panthor: Recover from panthor_gpu_flush_caches() failures
Unknown 0
CVE-2025-71313
PCI: endpoint: Add missing NULL check for alloc_workqueue()
Unknown 0
CVE-2025-71312
fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()
Unknown 0
CVE-2025-71311
fs/ntfs3: Initialize new folios before use
Unknown 0

Affected Vendor

Affected Software

Linux
Vulnerable Versions:
73a0d12114b4bc1a9def79a623264754b9df698e, 8a9c61c3ef187d8891225f9b932390670a43a0d3, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 5ef16d2d172ee56714cff37cd005b98aba08ef5a, ff169909eac9e00bf1aa0af739ba6ddfb1b1d135, 47244ac0b65bd74cc70007d8e1bac68bd2baad19, c45cea83e13699bdfd47842e04d09dd43af4c371, 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6, 5.10.82, 5.15.5, 4.4.293, 4.9.291, 4.14.256, 4.19.218, 5.4.162, 5.16, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19

Timeline

Official Publish: January 13th, 2026
Last Modified: July 14th, 2026
Added to House: July 22nd, 2026

CVSS Vectors

No vector data available

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.