nfc: nci: fix circular locking dependency in nci_close_device
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.2
References 8
git.kernel.org
- stable/c/7ed00a3edc8597fe2333f524401e2889aa1b5edf
- stable/c/5eef9ebec7f5738f12cadede3545c05b34bf5ac3
- stable/c/ca54e904a071aa65ef3ad46ba42d51aaac6b73b4
- stable/c/eb435d150ca74b4d40f77f1a2266f3636ed64a79
- stable/c/1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289
- stable/c/d89b74bf08f067b55c03d7f999ba0a0e73177eb3
- stable/c/09143c0e8f3b03517e6233aad42f45c794d8df8e
- stable/c/4527025d440ce84bf56e75ce1df2e84cb8178616