NVD / CVE Program· CNA Linux

CVE-2026-52982: net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit()

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Linux Linux 23f0e34c64acba15cad4d23e50f41f533da195fa, 24831b0b2ada9fef18d1f486b7b7c444ee5ba637, 30cf9829d09ca958279c937af8e35495cd2f1e09; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 23f0e34c64acba15cad4d23e50f41f533da195fa, 24831b0b2ada9fef18d1f486b7b7c444ee5ba637, 30cf9829d09ca958279c937af8e35495cd2f1e09; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Jun 24, 2026
Updated: Oct 19, 2026
EPSS: 0.5% · 45th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5af290c86fa81ddbc86a08d54229af5daa40c6a4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 24831b0b2ada9fef18d1f486b7b7c444ee5ba637affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 423b5b86e14e190f6e3161eb5f2ea5f908295ba7affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5db090ca07b28a63fb1499690cf19a3f3adafacbaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 30cf9829d09ca958279c937af8e35495cd2f1e09affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6999d70e0eda39af029fa1891c48f0a8832b09d5affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4dd7eb94f79486b77ca6b4c8676aedbc465dc802affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 23f0e34c64acba15cad4d23e50f41f533da195faaffected · git
- before 2.6.12not affected · semver

Affected versions · NVD (9)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel2.6.12.1 and later · before 5.10.258
linux linux kernel5.11 and later · before 5.15.209
linux linux kernel5.16 and later · before 6.1.175
linux linux kernel6.2 and later · before 6.6.141
linux linux kernel6.7 and later · before 6.12.91
linux linux kernel6.13 and later · before 6.18.33
linux linux kernel6.19 and later · before 7.0.10
linux linux kernel2.6.12
linux linux kernel7.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.176-1	6.1.176-1
Debian:13	linux	before 6.12.94-1	6.12.94-1
Debian:14	linux	before 7.0.10-1	7.0.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-52977Jun 24, 2026 · futex: Prevent lockup in requeue-PI during signal/ timeout wakeup
22Monitor
← EarlierCVE-2026-52981Jun 24, 2026 · neigh: let neigh_xmit take skb ownership
30Monitor
Later →CVE-2026-52983Jun 24, 2026 · net: airoha: fix BQL imbalance in TX path
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	23f0e34c64acba15cad4d23e50f41f533da195fa	Vendor (CNA)
Linux Linux	24831b0b2ada9fef18d1f486b7b7c444ee5ba637	Vendor (CNA)
Linux Linux	30cf9829d09ca958279c937af8e35495cd2f1e09	Vendor (CNA)
Linux Linux	423b5b86e14e190f6e3161eb5f2ea5f908295ba7	Vendor (CNA)
Linux Linux	4dd7eb94f79486b77ca6b4c8676aedbc465dc802	Vendor (CNA)
Linux Linux	5af290c86fa81ddbc86a08d54229af5daa40c6a4	Vendor (CNA)
Linux Linux	5db090ca07b28a63fb1499690cf19a3f3adafacb	Vendor (CNA)
Linux Linux	6999d70e0eda39af029fa1891c48f0a8832b09d5	Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.0	6.6.143.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.176-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (2)

SSVC exploitation— → noneOct 16, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/23f0e34c64acba15cad4d23e50f41f533da195fa

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records