net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit()
- 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.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 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
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() syzbot reported a KASAN slab-use-after-free read in rtl8150_start_xmit() when accessing skb->len for tx statistics after usb_submit_urb() has been called: BUG: KASAN: slab-use-after-free in rtl8150_start_xmit+0x71f/0x760 drivers/net/usb/rtl8150.c:712 Read of size 4 at addr ffff88810eb7a930 by task kworker/0:4/5226 The URB completion handler write_bulk_callback() frees the skb via dev_kfree_skb_irq(dev->tx_skb). The URB may complete on another CPU in softirq context before usb_submit_urb() returns in the submitter, so by the time the submitter reads skb->len the skb has already been queued to the per-CPU completion_queue and freed by net_tx_action(): CPU A (xmit) CPU B (USB completion softirq) ------------ ------------------------------ dev->tx_skb = skb; usb_submit_urb() --+ |-------> write_bulk_callback() | dev_kfree_skb_irq(dev->tx_skb) | net_tx_action() | napi_skb_cache_put() <-- free netdev->stats.tx_bytes | += skb->len; <-- UAF read Fix it by caching skb->len before submitting the URB and using the cached value when updating the tx_bytes counter. The pre-existing tx_bytes semantics are preserved: the counter tracks the original frame length (skb->len), not the ETH_ZLEN/USB-alignment padded "count" value that is handed to the device. Changing that would be a user-visible accounting change and is out of scope for this UAF fix.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5af290c86fa81ddbc86a08d54229af5daa40c6a4; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 24831b0b2ada9fef18d1f486b7b7c444ee5ba637; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 423b5b86e14e190f6e3161eb5f2ea5f908295ba7; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5db090ca07b28a63fb1499690cf19a3f3adafacb; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 30cf9829d09ca958279c937af8e35495cd2f1e09; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 6999d70e0eda39af029fa1891c48f0a8832b09d5; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 4dd7eb94f79486b77ca6b4c8676aedbc465dc802; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 23f0e34c64acba15cad4d23e50f41f533da195fa
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.141; From 6.7.0 · fixed in 6.12.91; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10
References 8
git.kernel.org
- stable/c/5af290c86fa81ddbc86a08d54229af5daa40c6a4
- stable/c/24831b0b2ada9fef18d1f486b7b7c444ee5ba637
- stable/c/423b5b86e14e190f6e3161eb5f2ea5f908295ba7
- stable/c/5db090ca07b28a63fb1499690cf19a3f3adafacb
- stable/c/30cf9829d09ca958279c937af8e35495cd2f1e09
- stable/c/6999d70e0eda39af029fa1891c48f0a8832b09d5
- stable/c/4dd7eb94f79486b77ca6b4c8676aedbc465dc802
- stable/c/23f0e34c64acba15cad4d23e50f41f533da195fa