nfc: pn533: hold a reference to the request skb during send_frame
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d329f61ad5786900334a54c2445dc99feda545bf, Kernel 19f1239758c23f087f4c25733cfcf62bf0b06051, Kernel 3e7a093c177f9f8b9fd039cab41191515079425a and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <d329f61ad5786900334a54c2445dc99feda545bf, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <19f1239758c23f087f4c25733cfcf62bf0b06051, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <3e7a093c177f9f8b9fd039cab41191515079425a, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <47792358a624ea066455ef86b744159928cd7716, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <753bdaf3220fe8371a6c3c75da645ea7753d11be, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <7a8e0a7aef80721da287ac246349aba7d98f6aed, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <7ee72c64b4b66b1b42dbddbca0a80a218f1b9297, >=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <8710faddef4ad8b2a6bfa985d896e2e1bfb77018, =4.7 | d329f61ad5786900334a54c2445dc99feda545bf, 19f1239758c23f087f4c25733cfcf62bf0b06051, 3e7a093c177f9f8b9fd039cab41191515079425a, 47792358a624ea066455ef86b744159928cd7716, 753bdaf3220fe8371a6c3c75da645ea7753d11be, 7a8e0a7aef80721da287ac246349aba7d98f6aed, 7ee72c64b4b66b1b42dbddbca0a80a218f1b9297, 8710faddef4ad8b2a6bfa985d896e2e1bfb77018 |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=4.7.0 <5.10.270 | 5.15.221, 6.1.188, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 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