CVE-2026-90222 — nfc: pn533: hold a reference to the request skb during send_frame
In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: hold a reference to the request skb during send_frame __pn533_send_async() publishes the command and then calls dev->phy_ops->send_frame(). Once dev->cmd is set, an incoming frame can be matched to this command: the I2C threaded IRQ runs pn533_recv_frame(), which queues cmd_complete_work, and pn533_send_async_complete() frees cmd->req with consume_skb(). On the I2C transport, pn533_i2c_send_frame() still dereferences the same skb after i2c_master_send() returns, so a completion that races the send can free the skb while the transport is still using it. The request skb is owned by the command object and may be freed by command completion at any time after dev->cmd is published, so the transport send path must not assume it stays alive. Hold a temporary reference to the request skb across the send_frame() call so the transport always sees a live skb even if completion races the send. Add a pn533_send_cmd_frame() helper and use it from all three send paths.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 8710faddef4ad8b2a6bfa985d896e2e1bfb77018≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 19f1239758c23f087f4c25733cfcf62bf0b06051≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 7ee72c64b4b66b1b42dbddbca0a80a218f1b9297≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 753bdaf3220fe8371a6c3c75da645ea7753d11be≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < d329f61ad5786900334a54c2445dc99feda545bf≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 7a8e0a7aef80721da287ac246349aba7d98f6aed≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 3e7a093c177f9f8b9fd039cab41191515079425a≥ 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc and < 47792358a624ea066455ef86b744159928cd7716 and 1 moreversion 4.7 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- nvd.nist.gov/vuln/detail/CVE-2026-90222
- github.com/advisories/GHSA-36pr-4p99-6568
- git.kernel.org/stable/c/8710faddef4ad8b2a6bfa985d896e2e1bfb77018
- git.kernel.org/stable/c/7a8e0a7aef80721da287ac246349aba7d98f6aed
- git.kernel.org/stable/c/3e7a093c177f9f8b9fd039cab41191515079425a
- git.kernel.org/stable/c/753bdaf3220fe8371a6c3c75da645ea7753d11be
- git.kernel.org/stable/c/7ee72c64b4b66b1b42dbddbca0a80a218f1b9297
- git.kernel.org/stable/c/d329f61ad5786900334a54c2445dc99feda545bf
- git.kernel.org/stable/c/47792358a624ea066455ef86b744159928cd7716
- git.kernel.org/stable/c/19f1239758c23f087f4c25733cfcf62bf0b06051
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 1d
- Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 1d
- Unknown CVE-2026-98863 KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90222 is "nfc: pn533: hold a reference to the request skb during send_frame", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.