CVE-2026-90224

published 17 Sep 2026 · updated 20 Nov 2026

nfc: nci: fix double completion race in nci_data_exchange_complete

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9030a1bbe2c6b1e3e54cef462d159b5248f09fd2, Kernel 6.1.188, Kernel 6.12.110 and 13 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=eb435d150ca74b4d40f77f1a2266f3636ed64a79 <9030a1bbe2c6b1e3e54cef462d159b5248f09fd2, >=6.1.168 <6.1.188, >=6.12.80 <6.12.110, >=6.18.21 <6.18.52, >=6.19.11 <6.20, >=6.6.131 <6.6.157, >=7ed00a3edc8597fe2333f524401e2889aa1b5edf <3f075832734005310740d148d1cf1c1e792ebdca, >=ca54e904a071aa65ef3ad46ba42d51aaac6b73b4 <cf646a9f5554bc07d6ccb59c327812b3a0c6a368, >=d89b74bf08f067b55c03d7f999ba0a0e73177eb3 <ba4c776af3dc21ed04e315e6545e99703bb1b53a, =09143c0e8f3b03517e6233aad42f45c794d8df8e, =7.0, >=1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289 <bfdf412208fea7fc0d5b32d68a35b25261917393, >=4527025d440ce84bf56e75ce1df2e84cb8178616 <8265a626cc14a48e46e6dc8c47667e72b4232ac2, >=4527025d440ce84bf56e75ce1df2e84cb8178616 <ee08414d78b851e3d1856d6e4d631939b01a1bbe, >=5.10.253 <5.10.270, >=5.15.203 <5.15.221, >=5eef9ebec7f5738f12cadede3545c05b34bf5ac3 <588ccd19a6e69eca72d54608c3ab3b45709b23059030a1bbe2c6b1e3e54cef462d159b5248f09fd2, 6.1.188, 6.12.110, 6.18.52, 6.20, 6.6.157, 3f075832734005310740d148d1cf1c1e792ebdca, cf646a9f5554bc07d6ccb59c327812b3a0c6a368, ba4c776af3dc21ed04e315e6545e99703bb1b53a, bfdf412208fea7fc0d5b32d68a35b25261917393, 8265a626cc14a48e46e6dc8c47667e72b4232ac2, ee08414d78b851e3d1856d6e4d631939b01a1bbe, 5.10.270, 5.15.221, 588ccd19a6e69eca72d54608c3ab3b45709b2305
linux-kernel: Kernel>=5.15.203 <5.15.221, >=6.1.168 <6.1.188, >=6.12.80 <6.12.110, >=6.18.21 <6.18.52, >=6.19.11 <6.20, >=6.6.131 <6.6.157, >=7.0.0 <7.2.6, >=5.10.253 <5.10.2705.15.221, 6.1.188, 6.12.110, 6.18.52, 6.20, 6.6.157, 7.2.6, 5.10.270

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90224 severity on Zeptric[![CVE-2026-90224](https://zeptric.io/badge/cve/CVE-2026-90224.svg)](https://zeptric.io/cve/CVE-2026-90224)