CVE-2026-89891

CVE CVE-2026-89891EUVD EUVD-2026-80491Published 2026-09-16T10:31:53.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.2.5; patch: 6.1.188; patch: 5.15.221; f410b4093fdd4d8f4644d3d486afe3040eceef7b <826915b6b65e2d3251e7248ea54289a22d748c84; patch: 6.6.157; f410b4093fdd4d8f4644d3d486afe3040eceef7b <da4b07da6281e39ce4c01e1227e036f3bf600e14; f410b4093fdd4d8f4644d3d486afe3040eceef7b <0782807552b6aff41b4656c6c9076a3231d3e79d; patch: 0; patch: 6.18.51; patch: 7.3-rc1; patch: 5.10.270; f410b4093fdd4d8f4644d3d486afe3040eceef7b <f61720346fdcc1a2deec59a2f6cbb0cc20d1dc18; f410b4093fdd4d8f4644d3d486afe3040eceef7b <20aacd87550be297dc39a3f9532dcfff91586510; 4.17; f410b4093fdd4d8f4644d3d486afe3040eceef7b <1ed575b1991f68569eb589b7747d3bc26aa6a8a2; f410b4093fdd4d8f4644d3d486afe3040eceef7b <20c2c65f3d9f7c278dc9750531d3201ac8bf78b7; patch: 6.12.110; f410b4093fdd4d8f4644d3d486afe3040eceef7b <16cb1ee17e093175b4d9ae33202f68e5b108cca2

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.