CVE-2026-89891 — media: em28xx: fix use-after-free of dev_next->devlist on disconnect
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < f61720346fdcc1a2deec59a2f6cbb0cc20d1dc18≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 1ed575b1991f68569eb589b7747d3bc26aa6a8a2≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < da4b07da6281e39ce4c01e1227e036f3bf600e14≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 20aacd87550be297dc39a3f9532dcfff91586510≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 20c2c65f3d9f7c278dc9750531d3201ac8bf78b7≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 0782807552b6aff41b4656c6c9076a3231d3e79d≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 16cb1ee17e093175b4d9ae33202f68e5b108cca2≥ f410b4093fdd4d8f4644d3d486afe3040eceef7b and < 826915b6b65e2d3251e7248ea54289a22d748c84 and 1 moreversion 4.17 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/0782807552b6aff41b4656c6c9076a3231d3e79d
- git.kernel.org/stable/c/826915b6b65e2d3251e7248ea54289a22d748c84
- git.kernel.org/stable/c/16cb1ee17e093175b4d9ae33202f68e5b108cca2
- git.kernel.org/stable/c/20aacd87550be297dc39a3f9532dcfff91586510
- nvd.nist.gov/vuln/detail/CVE-2026-89891
- git.kernel.org/stable/c/da4b07da6281e39ce4c01e1227e036f3bf600e14
- git.kernel.org/stable/c/1ed575b1991f68569eb589b7747d3bc26aa6a8a2
- git.kernel.org/stable/c/20c2c65f3d9f7c278dc9750531d3201ac8bf78b7
- git.kernel.org/stable/c/f61720346fdcc1a2deec59a2f6cbb0cc20d1dc18
- github.com/advisories/GHSA-5cx6-377w-hc5f
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 1h
- Unknown CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 1h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 3d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 3d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 3d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89891 is "media: em28xx: fix use-after-free of dev_next->devlist on disconnect", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.