Review reviewCritical

CVE-2026-52982

Linux Linux, linux kernel

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 conte...

CVSS
9.8
EPSS
0.54%
42.1% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.54%
Technical severityCVSS 9.8

Vulnerability overview

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 conte...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5af290c86fa81ddbc86a08d54229af5daa40c6a4, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 24831b0b2ada9fef18d1f486b7b7c444ee5ba637, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 423b5b86e14e190f6e3161eb5f2ea5f908295ba7, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5db090ca07b28a63fb1499690cf19a3f3adafacb, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 30cf9829d09ca958279c937af8e35495cd2f1e09, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6999d70e0eda39af029fa1891c48f0a8832b09d5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4dd7eb94f79486b77ca6b4c8676aedbc465dc802, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 23f0e34c64acba15cad4d23e50f41f533da195fa, >= 2.6.12, >= 2.6.12.1 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10, 2.6.12, 7.1
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416