{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89741 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89741 is a high-severity use after free vulnerability in Linux, published on 11 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-89741 and fix it if it is affected.\n\nWhat it is: CVE-2026-89741 is a high-severity use after free vulnerability in Linux, published on 11 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-89741 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-89741/ (Markdown: https://insights.sbomify.com/CVE-2026-89741/index.md)","id":"CVE-2026-89741","markdown":"https://insights.sbomify.com/CVE-2026-89741/index.md","name":"CVE-2026-89741","record":{"aliases":["AZL-100433","BELL-CVE-2026-89741","DEBIAN-CVE-2026-89741","GHSA-x4c4-qfr2-c3vv","UBUNTU-CVE-2026-89741"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A double-free vulnerability in the Linux kernel's V4L2 subsystem allows attackers to potentially execute code or cause a system crash.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"media: v4l2-dev: fix error handling in __video_register_device()\"\n\nThis reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.\n\nThe intentions of that patch were good, but it doesn't work.\n\nThe idea is that if device_register fails, you have to do a put_device\nto let the ref counter release resources.\n\nHowever, the V4L2 API says that if video_register_device() fails, then\nyou have to call video_device_release(), which kfree()s the video_device\nstruct.\n\nBut the put_device() will already have freed the struct, so you end\nup in a double-free scenario.\n\nThere is not really a good way of fixing this without breaking\nvideo_register_device() into two parts, one that initializes everything,\nand one that does the actual device_register, and then converting all\nV4L2 drivers to this new model.\n\nThat is a massive job, and it is very unlikely that device_register\nwill fail.\n\nSo rather than ending up in a double-free scenario, just revert this\npatch, and in that case we'll have a small memory leak. Which is a lot\nmore robust.","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":"Revert \"media: v4l2-dev: fix error handling in __video_register_device()\"","id":"CVE-2026-89741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"rapidio: mport_cdev: fix use-after-free in dma_req_free()","id":"CVE-2026-89742"},"packages":[],"prev":{"headline":"serial: imx: serialize imx_uart_ports[] lifetime","id":"CVE-2026-89740"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A double-free vulnerability in the Linux kernel's V4L2 subsystem allows attackers to potentially execute code or cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-89741/"}