CVE-2026-89891

media: em28xx: fix use-after-free of dev_next->devlist on disconnect

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: media: em28xx: fix use-after-free of dev_next->devlist on disconnect When a device with has_dual_ts=1 is probed and the is_audio_only path is taken, both dev and dev->dev_next are added to the global em28xx_devlist via em28xx_init_extension(). However, during disconnect, em28xx_close_extension(dev) only calls list_del(&dev->devlist), leaving dev->dev_next->devlist still linked in the global list. When dev_next is subsequently freed via kref_put(), its devlist entry becomes a dangling pointer in em28xx_devlist. The next device probe that calls em28xx_init_extension() triggers a list corruption BUG when list_add_tail detects the freed node. This bug was exposed by commit a368ecde8a50 ("USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor") which clears reserved bits in bEndpointAddress during endpoint parsing. This causes fuzzed endpoint addresses like 0xf3 to be normalized to 0x83, which em28xx interprets as a vendor audio endpoint, enabling the is_audio_only + has_dual_ts code path that was previously unreachable with such descriptors. Fix this by removing dev->dev_next->devlist from the global list in em28xx_close_extension() before the device is freed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.17f410b4093fdd4d8f4644d3d486afe3040eceef7b
Vendor states this is fixed in 0782807552b6aff41b4656c6c9076a3231d3e79d (fixed)
Vendor states this is fixed in 16cb1ee17e093175b4d9ae33202f68e5b108cca2 (fixed)
Vendor states this is fixed in 1ed575b1991f68569eb589b7747d3bc26aa6a8a2 (fixed)
Vendor states this is fixed in 20aacd87550be297dc39a3f9532dcfff91586510 (fixed)
Vendor states this is fixed in 20c2c65f3d9f7c278dc9750531d3201ac8bf78b7 (fixed)
Vendor states this is fixed in 826915b6b65e2d3251e7248ea54289a22d748c84 (fixed)
Vendor states this is fixed in da4b07da6281e39ce4c01e1227e036f3bf600e14 (fixed)
Vendor states this is fixed in f61720346fdcc1a2deec59a2f6cbb0cc20d1dc18 (fixed)
Vendor states this is fixed in 4.17 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card