CVE-2026-90224: nfc: nci: fix double completion race in nci_data_exchange_complete
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 3f075832734005310740d148d1cf1c1e792ebdca, 5.10.270, 5.15.221.
Low priority for now. Upgrade to Linux Linux 3f075832734005310740d148d1cf1c1e792ebdca, 5.10.270, 5.15.221 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 09143c0e8f3b03517e6233aad42f45c794d8df8e, 7.0affected
- 7ed00a3edc8597fe2333f524401e2889aa1b5edf and later · before 3f075832734005310740d148d1cf1c1e792ebdcaaffected · git
- 5eef9ebec7f5738f12cadede3545c05b34bf5ac3 and later · before 588ccd19a6e69eca72d54608c3ab3b45709b2305affected · git
- ca54e904a071aa65ef3ad46ba42d51aaac6b73b4 and later · before cf646a9f5554bc07d6ccb59c327812b3a0c6a368affected · git
- eb435d150ca74b4d40f77f1a2266f3636ed64a79 and later · before 9030a1bbe2c6b1e3e54cef462d159b5248f09fd2affected · git
- 1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289 and later · before bfdf412208fea7fc0d5b32d68a35b25261917393affected · git
- d89b74bf08f067b55c03d7f999ba0a0e73177eb3 and later · before ba4c776af3dc21ed04e315e6545e99703bb1b53aaffected · git
- 4527025d440ce84bf56e75ce1df2e84cb8178616 and later · before ee08414d78b851e3d1856d6e4d631939b01a1bbeaffected · git
- 4527025d440ce84bf56e75ce1df2e84cb8178616 and later · before 8265a626cc14a48e46e6dc8c47667e72b4232ac2affected · git
- 5.10.253 and later · before 5.10.270affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90222Sep 17, 2026 · nfc: pn533: hold a reference to the request skb during send_frame0Monitor
- ← EarlierCVE-2026-90223Sep 17, 2026 · nfc: llcp: bound SNL TLV parsing to the skb and add length checks28Monitor
- Later →CVE-2026-90225Sep 17, 2026 · nfc: llcp: read llcp_sock->local under the socket lock in getsockopt31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3f075832734005310740d148d1cf1c1e792ebdca | Vendor (CNA) |
| Linux Linux | 5.10.270 | Vendor (CNA) |
| Linux Linux | 5.15.221 | Vendor (CNA) |
| Linux Linux | 588ccd19a6e69eca72d54608c3ab3b45709b2305 | Vendor (CNA) |
| Linux Linux | 6.1.188 | Vendor (CNA) |
| Linux Linux | 6.12.110 | Vendor (CNA) |
| Linux Linux | 6.18.52 | Vendor (CNA) |
| Linux Linux | 6.20 | Vendor (CNA) |
| Linux Linux | 6.6.157 | Vendor (CNA) |
| Linux Linux | 8265a626cc14a48e46e6dc8c47667e72b4232ac2 | Vendor (CNA) |
| Linux Linux | 9030a1bbe2c6b1e3e54cef462d159b5248f09fd2 | Vendor (CNA) |
| Linux Linux | ba4c776af3dc21ed04e315e6545e99703bb1b53a | Vendor (CNA) |
| Linux Linux | bfdf412208fea7fc0d5b32d68a35b25261917393 | Vendor (CNA) |
| Linux Linux | cf646a9f5554bc07d6ccb59c327812b3a0c6a368 | Vendor (CNA) |
| Linux Linux | ee08414d78b851e3d1856d6e4d631939b01a1bbe | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/588ccd19a6e69eca72d54608c3ab3b45709b2305
- git.kernel.org/stable/c/8265a626cc14a48e46e6dc8c47667e72b4232ac2
- git.kernel.org/stable/c/9030a1bbe2c6b1e3e54cef462d159b5248f09fd2
- git.kernel.org/stable/c/ba4c776af3dc21ed04e315e6545e99703bb1b53a
- git.kernel.org/stable/c/bfdf412208fea7fc0d5b32d68a35b25261917393
- git.kernel.org/stable/c/cf646a9f5554bc07d6ccb59c327812b3a0c6a368
- git.kernel.org/stable/c/ee08414d78b851e3d1856d6e4d631939b01a1bbe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.