nfc: pn533: allocate rx skb before consuming bytes
- 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
- 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: 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.5
References 8
git.kernel.org
- stable/c/2ca64fb7e2d2ae14619dd204d4f2f0a601f421fb
- stable/c/8b71299d587d9e4c830c18afb884c80ddb30ad28
- stable/c/16649adc2e19509104245ea1f349b629d858f11f
- stable/c/07cb6c72e66ba548679f22ac29ad588da8999279
- stable/c/a9495069b43b8634c1ae0042e888766c34f66637
- stable/c/21ae2cda66a55c759607bbf1d23cbaa42019d2de
- stable/c/7e37da42eda45d7859d9273fc7e225d8df458038
- stable/c/c71ba669b570c7b3f86ec875be222ea11dacb352