GHSA-3CP8-QX5M-J98G
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In 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.
{
"affected": [],
"aliases": [
"CVE-2026-89900"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:58Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: cec: core: Fix kmemleak due to missed rc_free_device() call\n\nThe commit dccc0c3ddf8f (\"media: rc: fix race between unregister and\nurb/irq callbacks\") removed the implicit call to rc_free_device() from\nrc_unregister_device(). However, the commit missed to remove the NULL\nassignment of adap-\u003erc that is now causing rc_free_device() to never be\ncalled on an allocated rc device.\n\nkmemleak reports following after e.g. dw-hdmi unbind:\n\nunreferenced object 0xffff00010ac10000 (size 4096):\n comm \"kworker/u16:1\", pid 39, jiffies 4294897739\n hex dump (first 32 bytes):\n 20 23 4b 0a 01 00 ff ff 08 00 c1 0a 01 00 ff ff #K.............\n 08 00 c1 0a 01 00 ff ff 00 00 00 00 00 00 00 00 ................\n backtrace (crc e11baccc):\n kmemleak_alloc+0x38/0x44\n __kmalloc_cache_noprof+0x4a8/0x5e0\n rc_allocate_device+0x48/0x2a0\n cec_allocate_adapter+0x3ac/0x800\n dw_hdmi_cec_probe+0x264/0x634\n platform_probe+0xc0/0x188\n really_probe+0x4a4/0x8e0\n __driver_probe_device+0x2f8/0x440\n driver_probe_device+0x60/0x160\n __device_attach_driver+0x1a0/0x2a0\n bus_for_each_drv+0x100/0x1a0\n __device_attach+0x174/0x350\n device_initial_probe+0x90/0xb0\n bus_probe_device+0x4c/0x120\n device_add+0xdec/0x116c\n platform_device_add+0x354/0x598\n\nRemove the assignment of adap-\u003erc to NULL to let cec_delete_adapter()\nfree the allocated rc device after last user of the cec device exits to\nfix the kmemleak.",
"id": "GHSA-3cp8-qx5m-j98g",
"modified": "2026-09-16T12:30:40Z",
"published": "2026-09-16T12:30:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89900"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/695063fc57574dd117b1bc750ca189cf03a2caad"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/954ee95a03b4d31d4505591bfaba02c24b75776b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a24ba0653f7154e671dc8d2bf64682ab2d042792"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cca2407794795cecff7f8e5f5a79f4ef6b1d6f6c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f28a8e1ba4d67a18e4662e5acefd5a4389322366"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.