{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89900 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89900 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89900 and fix it if it is affected.\n\nWhat it is: CVE-2026-89900 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89900 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89900/ (Markdown: https://insights.sbomify.com/CVE-2026-89900/index.md)","id":"CVE-2026-89900","markdown":"https://insights.sbomify.com/CVE-2026-89900/index.md","name":"CVE-2026-89900","record":{"aliases":["AZL-101120","BELL-CVE-2026-89900","DEBIAN-CVE-2026-89900","GHSA-3cp8-qx5m-j98g","UBUNTU-CVE-2026-89900"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory leak in the Linux kernel CEC driver can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"media: cec: core: Fix kmemleak due to missed rc_free_device() call","id":"CVE-2026-89900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref","id":"CVE-2026-89901"},"packages":[],"prev":{"headline":"media: cec: disable delayed work before freeing an interrupted transmit","id":"CVE-2026-89899"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel CEC driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-89900/"}