CVE-2026-89891

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Vendor Advisories for CVE-2026-89891(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-02 20:42 UTCVendor advisory
  3. 2026-10-02 20:42 UTCGHSA enrichment
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 03:01 UTCEG score recompute
  7. 2026-09-30 03:01 UTCVendor advisory
  8. 2026-09-30 03:01 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:49 UTCEPSS rescore
  12. 2026-09-27 09:31 UTCVendor advisory
  13. 2026-09-27 09:31 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 15:59 UTCVendor advisory
  16. 2026-09-24 15:59 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-22 16:01 UTCEPSS rescore
  20. 2026-09-21 22:28 UTCVendor advisory
  21. 2026-09-21 22:27 UTCGHSA enrichment
  22. 2026-09-21 21:09 UTCEPSS rescore
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 04:56 UTCEG score recompute
  25. 2026-09-19 04:56 UTCVendor advisory
Show 6 more
  1. 2026-09-19 04:56 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-16 11:21 UTCNVD update
  5. 2026-09-16 10:39 UTCEG score recompute
  6. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89891?
CVE-2026-89891 is a publicly disclosed vulnerability published on September 16, 2026. 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 hasdualts=1 is probed and the isaudioonly path is taken, both dev and dev->dev_next are added to the global em28xxdevlist via…
When was CVE-2026-89891 disclosed?
CVE-2026-89891 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89891 actively exploited?
CVE-2026-89891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89891?
No fix for CVE-2026-89891 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-89891 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89891

Explore →

Is Your Infrastructure Affected by CVE-2026-89891?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.