CVE-2026-89892

media: em28xx: defer audio-only extension registration

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: defer audio-only extension registration The audio-only path registers extensions while probing the primary device. For a dual-TS board, this happens before dev_next is created. The duplicate device inherits is_audio_only and is then independently inserted into em28xx_devlist. The list is intended to contain only primary devices: extension operations reach the secondary device through dev_next. The independently linked secondary can be freed during disconnect while its list node remains reachable, resulting in a use-after-free. Defer audio-only extension registration to the module-request work item. It runs only after probing has completed construction of the optional secondary device, so only the primary is registered and extension callbacks reach the secondary through dev_next.

Affected

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

4.174a089668ef22c295ed4997289cc48446c849249c
Vendor states this is fixed in 0da1e627f4fc9d0e947fdae90913042120878923 (fixed)
Vendor states this is fixed in 1abe9524dec0fd26e9ceb8d586034d6f68dd8273 (fixed)
Vendor states this is fixed in 4666197ca4f7d80cd3b0292054fe45d76be9ba04 (fixed)
Vendor states this is fixed in 4e11c45dfdc72ab656067b1df8fcebaf52fd4715 (fixed)
Vendor states this is fixed in 95f76f51937fdfb0fc1e14cae606b1ef574a56f3 (fixed)
Vendor states this is fixed in d06067ee32620f272cfb80c7bc7c572ad4e74724 (fixed)
Vendor states this is fixed in f8d7e77d9c621b42a191c67a9b37bec23dc1d555 (fixed)
Vendor states this is fixed in f9322ac9f862961d7f377b87ec26c8565af7e073 (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