nfc: pn533: allocate rx skb before consuming bytes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c656aa4c27b17a8c70da223ed5ab42145800d6b5 · < 21ae2cda66a55c759607bbf1d23cbaa42019d2de| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfc: pn533: allocate rx skb before consuming bytes
pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer.
If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().
Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.
From the CVE record · Linux
The pn533 NFC driver can report that it accepted no bytes after consuming a frame if receive-buffer allocation fails. A subsequent receive callback can then dereference a NULL pointer; the input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running Linux kernels with the pn533 NFC driver should check their exposure; affected versions are not specified.