CVE-2026-90224

nfc: nci: fix double completion race in nci_data_exchange_complete

HIGH
7.5
CVSS Score
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix double completion race in nci_data_exchange_complete nci_close_device() and nci_rx_work can both call nci_data_exchange_complete() concurrently. After commit 4527025d440ce8 ("nfc: nci: fix circular locking dependency in nci_close_device") moved flush_workqueue(ndev->rx_wq) after mutex_unlock(&ndev->req_lock), rx_work is no longer serialized with the explicit completion call in the close path. Both callers read the non-NULL callback pointer and invoke rawsock_data_exchange_complete(), which calls sock_put() -- but only one sock_hold() was taken, so the second sock_put() underflows the refcount and frees the socket while it is still in use. Replace the bare clear_bit(NCI_DATA_EXCHANGE) with test_and_clear_bit() so that only the first caller proceeds to invoke the callback.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

09143c0e8f3b03517e6233aad42f45c794d8df8e1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb12894527025d440ce84bf56e75ce1df2e84cb81786165.10.2535.15.2035eef9ebec7f5738f12cadede3545c05b34bf5ac36.1.1686.12.806.18.216.19.116.6.1317.07ed00a3edc8597fe2333f524401e2889aa1b5edf9143c0e8f3b3517e6233aad42f45c794d8df8eca54e904a071aa65ef3ad46ba42d51aaac6b73b4d89b74bf08f067b55c03d7f999ba0a0e73177eb3eb435d150ca74b4d40f77f1a2266f3636ed64a79
Vendor states this is fixed in 3f075832734005310740d148d1cf1c1e792ebdca (fixed)
Vendor states this is fixed in 588ccd19a6e69eca72d54608c3ab3b45709b2305 (fixed)
Vendor states this is fixed in 8265a626cc14a48e46e6dc8c47667e72b4232ac2 (fixed)
Vendor states this is fixed in 9030a1bbe2c6b1e3e54cef462d159b5248f09fd2 (fixed)
Vendor states this is fixed in ba4c776af3dc21ed04e315e6545e99703bb1b53a (fixed)
Vendor states this is fixed in bfdf412208fea7fc0d5b32d68a35b25261917393 (fixed)
Vendor states this is fixed in cf646a9f5554bc07d6ccb59c327812b3a0c6a368 (fixed)
Vendor states this is fixed in ee08414d78b851e3d1856d6e4d631939b01a1bbe (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card