CVE-2026-52982net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit()
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 5af290c86fa81ddbc86a08d54229af5daa40c6a4; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 24831b0b2ada9fef18d1f486b7b7c444ee5ba637; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 423b5b86e14e190f6e3161eb5f2ea5f908295ba7; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 5db090ca07b28a63fb1499690cf19a3f3adafacb; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 30cf9829d09ca958279c937af8e35495cd2f1e09; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 6999d70e0eda39af029fa1891c48f0a8832b09d5; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 4dd7eb94f79486b77ca6b4c8676aedbc465dc802; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 23f0e34c64acba15cad4d23e50f41f533da195fa | CNA record |
linux linux_kernel linux:linux_kernel | from 2.6.12.1 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.141; from 6.7 before 6.12.91; from 6.13 before 6.18.33; from 6.19 before 7.0.10; 2.6.12; and 5 more ranges | NVD |
References
- https://git.kernel.org/stable/c/5af290c86fa81ddbc86a08d54229af5daa40c6a4patch
- https://git.kernel.org/stable/c/24831b0b2ada9fef18d1f486b7b7c444ee5ba637patch
- https://git.kernel.org/stable/c/423b5b86e14e190f6e3161eb5f2ea5f908295ba7patch
- https://git.kernel.org/stable/c/5db090ca07b28a63fb1499690cf19a3f3adafacbpatch
- https://git.kernel.org/stable/c/30cf9829d09ca958279c937af8e35495cd2f1e09patch
- https://git.kernel.org/stable/c/6999d70e0eda39af029fa1891c48f0a8832b09d5patch
- https://git.kernel.org/stable/c/4dd7eb94f79486b77ca6b4c8676aedbc465dc802patch
- https://git.kernel.org/stable/c/23f0e34c64acba15cad4d23e50f41f533da195fapatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.