nfc: pn533: hold a reference to the request skb during send_frame
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 8710faddef4ad8b2a6bfa985d896e2e1bfb77018; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 19f1239758c23f087f4c25733cfcf62bf0b06051; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 7ee72c64b4b66b1b42dbddbca0a80a218f1b9297; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 753bdaf3220fe8371a6c3c75da645ea7753d11be; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in d329f61ad5786900334a54c2445dc99feda545bf; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 7a8e0a7aef80721da287ac246349aba7d98f6aed; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 3e7a093c177f9f8b9fd039cab41191515079425a; From 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc · fixed in 47792358a624ea066455ef86b744159928cd7716
- Linux Linux
4.7
- KernelLinux
From 4.7.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/8710faddef4ad8b2a6bfa985d896e2e1bfb77018
- stable/c/19f1239758c23f087f4c25733cfcf62bf0b06051
- stable/c/7ee72c64b4b66b1b42dbddbca0a80a218f1b9297
- stable/c/753bdaf3220fe8371a6c3c75da645ea7753d11be
- stable/c/d329f61ad5786900334a54c2445dc99feda545bf
- stable/c/7a8e0a7aef80721da287ac246349aba7d98f6aed
- stable/c/3e7a093c177f9f8b9fd039cab41191515079425a
- stable/c/47792358a624ea066455ef86b744159928cd7716