HOMEVULNERABILITIESCVE-2026-52982
CRITICAL

CVE-2026-52982

Published: June 24, 2026· Updated: Jun 28, 2026

9.8
CVSS v3.1
EPSS:0.18%probability of exploitation in 30 daysPercentile:8.2th

Official Description

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.

NVD Source

Technical Analysis

CVE-2026-52982 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.

A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.8.

CVSS v3.1 Vector Breakdown

Exploitability
Attack VectorNetwork
Attack ComplexityLow
Privileges Req.None
User InteractionNone
ScopeUnchanged
Impact
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected Vendors & Products

Mentioned vendors (from description):
Linux
CPE data not yet available in NVD for this CVE.

Exploit & PoC Resources

NO KNOWN EXPLOITNo public exploit confirmed at this time
External links open in a new tab. Always verify in a controlled environment before use.

All References (8)

Quick Facts

CVE IDCVE-2026-52982
CVSS Score9.8 / 10
SeverityCRITICAL
CISA KEVNo
EPSS (30d)0.18%
PublishedJun 24, 2026

Recommended Actions

  • Apply vendor patches immediately
  • Monitor CVE-2026-52982 in threat intel feeds
  • Review IDS/IPS signatures for exploitation attempts
Data sourced from NVD (NIST), CISA KEV, and EPSS (FIRST). Analysis generated by CTIWATCH.COM. CVE data is provided under the NVD usage policy.