CVE-2026-90222

nfc: pn533: hold a reference to the request skb during send_frame

N/A
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
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

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

4.79815c7cf22daceabfb919ddcd6f2c80e049c1fbc
Vendor states this is fixed in 19f1239758c23f087f4c25733cfcf62bf0b06051 (fixed)
Vendor states this is fixed in 3e7a093c177f9f8b9fd039cab41191515079425a (fixed)
Vendor states this is fixed in 47792358a624ea066455ef86b744159928cd7716 (fixed)
Vendor states this is fixed in 753bdaf3220fe8371a6c3c75da645ea7753d11be (fixed)
Vendor states this is fixed in 7a8e0a7aef80721da287ac246349aba7d98f6aed (fixed)
Vendor states this is fixed in 7ee72c64b4b66b1b42dbddbca0a80a218f1b9297 (fixed)
Vendor states this is fixed in 8710faddef4ad8b2a6bfa985d896e2e1bfb77018 (fixed)
Vendor states this is fixed in d329f61ad5786900334a54c2445dc99feda545bf (fixed)
Vendor states this is fixed in 4.7 (unaffected)
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)
Vendor states this is fixed in 6.6.157 (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.

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