CVE-2026-89900

CVE CVE-2026-89900EUVD EUVD-2026-80500Published 2026-09-16T10:32:00.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: media: cec: core: Fix kmemleak due to missed rc_free_device() call The commit dccc0c3ddf8f ("media: rc: fix race between unregister and urb/irq callbacks") removed the implicit call to rc_free_device() from rc_unregister_device(). However, the commit missed to remove the NULL assignment of adap->rc that is now causing rc_free_device() to never be called on an allocated rc device. kmemleak reports following after e.g. dw-hdmi unbind: unreferenced object 0xffff00010ac10000 (size 4096): comm "kworker/u16:1", pid 39, jiffies 4294897739 hex dump (first 32 bytes): 20 23 4b 0a 01 00 ff ff 08 00 c1 0a 01 00 ff ff #K............. 08 00 c1 0a 01 00 ff ff 00 00 00 00 00 00 00 00 ................ backtrace (crc e11baccc): kmemleak_alloc+0x38/0x44 __kmalloc_cache_noprof+0x4a8/0x5e0 rc_allocate_device+0x48/0x2a0 cec_allocate_adapter+0x3ac/0x800 dw_hdmi_cec_probe+0x264/0x634 platform_probe+0xc0/0x188 really_probe+0x4a4/0x8e0 __driver_probe_device+0x2f8/0x440 driver_probe_device+0x60/0x160 __device_attach_driver+0x1a0/0x2a0 bus_for_each_drv+0x100/0x1a0 __device_attach+0x174/0x350 device_initial_probe+0x90/0xb0 bus_probe_device+0x4c/0x120 device_add+0xdec/0x116c platform_device_add+0x354/0x598 Remove the assignment of adap->rc to NULL to let cec_delete_adapter() free the allocated rc device after last user of the cec device exits to fix the kmemleak.

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 6.6.143 <6.6.157; patch: 6.18.51; patch: 6.6.157; patch: 0; patch: 7.3-rc1; patch: 6.12.110; e250b672d40a9e0d97a8895cbb301248bea0fce6 <695063fc57574dd117b1bc750ca189cf03a2caad; 75977f5f5c4974c72bbedefbf09ad33ebbaa36f1 <f28a8e1ba4d67a18e4662e5acefd5a4389322366; 6.12.93 <6.12.110; dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 <a24ba0653f7154e671dc8d2bf64682ab2d042792; 7.1; 6.18.35 <6.18.51; patch: 7.2.5; a7becb58f6b8a3a3efe5d3acfd52e2c107de6772 <954ee95a03b4d31d4505591bfaba02c24b75776b; dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 <cca2407794795cecff7f8e5f5a79f4ef6b1d6f6c

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

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

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.