In the Linux kernel, the following vulnerability has been resolved:
nfc: nci: fix circular locking dependency in nci_close_device
nci_close_device() flushes rx_wq and tx_wq while holding req_lock.
This causes a circular locking dependency because nci_rx_work()
running on rx_wq can end up taking req_lock too:
nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete
-> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target
-> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock)
Move the flush of rx_wq after req_lock has been released.
This should safe (I think) because NCI_UP has already been cleared
and the transport is closed, so the work will see it and return
-ENETDOWN.
NIPA has been hitting this running the nci selftest with a debug
kernel on roughly 4% of the runs.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-22 14:16
Updated : 2026-06-17 10:33
NVD link : CVE-2026-31509
Mitre link : CVE-2026-31509
CVE.ORG link : CVE-2026-31509
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking
