{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89724 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89724 is a high-severity memory corruption 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-89724 and fix it if it is affected.\n\nWhat it is: CVE-2026-89724 is a high-severity memory corruption 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-89724 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-89724/ (Markdown: https://insights.sbomify.com/CVE-2026-89724/index.md)","id":"CVE-2026-89724","markdown":"https://insights.sbomify.com/CVE-2026-89724/index.md","name":"CVE-2026-89724","record":{"aliases":["AZL-100483","BELL-CVE-2026-89724","DEBIAN-CVE-2026-89724","GHSA-8cqc-p4qr-2jqq","UBUNTU-CVE-2026-89724"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel media driver","requires_auth":"low_privilege","summary":"An out-of-bounds write in the Linux kernel vicodec driver allows attackers to corrupt kernel heap memory, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nmedia: vicodec: fix out-of-bounds write in FWHT encoder\n\nvidioc_s_fmt_vid_out() sizes the encoder CAPTURE buffer from the\ncompressed descriptor pixfmt_fwht, whose sizeimage_mult is 3:\ncoded_w * coded_h * 3 + sizeof(struct fwht_cframe_hdr). fwht_encode_frame()\nencodes one plane per component, and an incompressible plane takes the\nFWHT_FRAME_UNENCODED path in encode_plane(), copying the plane verbatim.\n\nFor a 4-component pixel format all four planes are full resolution\n(width_div == height_div == 1), so a frame that forces every plane\nthrough the unencoded fallback writes\nsizeof(struct fwht_cframe_hdr) + 4 * coded_w * coded_h bytes, overrunning\nthe plane by coded_w * coded_h, which can result in corruption\nof adjacent kernel heap memory.\n\nBump pixfmt_fwht.sizeimage_mult from 3 to 4, matching the largest\ncomponents_num among the supported raw formats, so the capture buffer is\nalways large enough for the unencoded fallback.","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: vicodec: fix out-of-bounds write in FWHT encoder","id":"CVE-2026-89724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"media: cec: stm32: prevent out-of-bounds write on RX overflow","id":"CVE-2026-89725"},"packages":[],"prev":{"headline":"nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation","id":"CVE-2026-89723"},"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":"An out-of-bounds write in the Linux kernel vicodec driver allows attackers to corrupt kernel heap memory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89724/"}