CVE-2025-71079

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write<br /> <br /> A deadlock can occur between nfc_unregister_device() and rfkill_fop_write()<br /> due to lock ordering inversion between device_lock and rfkill_global_mutex.<br /> <br /> The problematic lock order is:<br /> <br /> Thread A (rfkill_fop_write):<br /> rfkill_fop_write()<br /> mutex_lock(&amp;rfkill_global_mutex)<br /> rfkill_set_block()<br /> nfc_rfkill_set_block()<br /> nfc_dev_down()<br /> device_lock(&amp;dev-&gt;dev) dev)<br /> rfkill_unregister()<br /> mutex_lock(&amp;rfkill_global_mutex) <br /> rfkill_global_mutex via rfkill_register) is safe because during<br /> registration the device is not yet in rfkill_list, so no concurrent<br /> rfkill operations can occur on this device.