nfc: s3fwrn5: 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: s3fwrn5: allocate rx skb before consuming bytes s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete 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.11
References 7
git.kernel.org
- stable/c/20a57de2e79b797ed75382659d52bf4c7d9cb446
- stable/c/e4ab0fd1c91882f2a7846b1817781c8741f7f315
- stable/c/d8c2aa3c4a1ec530a485e46a1c4f1a118bb00156
- stable/c/7c31f7a599cf00fad3c204092a91a924126c67e4
- stable/c/6d931680a9851481c3243689488eafed08eeff71
- stable/c/09822d3d6f68a0cdc4626e0c507324a4927f55a9
- stable/c/5c14a19d5b1645cce1cb1252833d70b23635b632