Back to CVE records
Medium 5.5Published Jan 13, 2026

CVE-2025-71079net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write

Updated under an hour ago ()

Does this affect you?

It affects Linux and 4 other products. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Oct 15, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
73a0d12114b4bc1a9def79a623264754b9df698e builds before 2e0831e9fc46a06daa6d4d8d57a2738e343130c3; from 8a9c61c3ef187d8891225f9b932390670a43a0d3 before e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012; from 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 before ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5; from 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 before 6b93c8ab6f6cda8818983a4ae3fcf84b023037b4; from 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 before 8fc4632fb508432895430cd02b38086bdd649083; from 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 before f3a8a7c1aa278f2378b2f3a10500c6674dffdfda; 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 builds before 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5; 5ef16d2d172ee56714cff37cd005b98aba08ef5a; and 11 more ranges
CNA record
Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP
siemens:simatic_s7_1500_cpu_1518_4_pn_dp_mfp (from the name)
from V3.1.6
CISA ADP
Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP
siemens:simatic_s7_1500_cpu_1518f_4_pn_dp_mfp (from the name)
from V3.1.6
CISA ADP
Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
siemens:siplus_s7_1500_cpu_1518_4_pn_dp_mfp (from the name)
from V3.1.6
CISA ADP
linux linux_kernel
linux:linux_kernel
from 4.4.293 before 4.5; from 4.9.291 before 4.10; from 4.14.256 before 4.15; from 4.19.218 before 4.20; from 5.4.162 before 5.5; from 5.10.82 before 5.10.248; from 5.15.5 before 5.15.198; from 5.16.1 before 6.1.160; and 12 more ranges
NVD

References

  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.