{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89725 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89725 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-89725 and fix it if it is affected.\n\nWhat it is: CVE-2026-89725 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-89725 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-89725/ (Markdown: https://insights.sbomify.com/CVE-2026-89725/index.md)","id":"CVE-2026-89725","markdown":"https://insights.sbomify.com/CVE-2026-89725/index.md","name":"CVE-2026-89725","record":{"aliases":["BELL-CVE-2026-89725","DEBIAN-CVE-2026-89725","GHSA-946x-47hf-5c7p","UBUNTU-CVE-2026-89725"],"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 CEC driver","requires_auth":"none","summary":"A remote CEC peer can trigger an out-of-bounds write in the STM32 CEC driver, potentially leading to kernel memory corruption and privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/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: cec: stm32: prevent out-of-bounds write on RX overflow\n\nstm32_rx_done() appends each received CEC byte to rx_msg.msg[] using\nrx_msg.len as the write index, incrementing it on every RXBR\n(receive-byte-ready) interrupt without checking it against the buffer\nsize:\n\n\tcec-\u003erx_msg.msg[cec-\u003erx_msg.len++] = val \u0026 0xFF;\n\nrx_msg.msg[] is a fixed CEC_MAX_MSG_SIZE (16) byte array in struct\ncec_msg, and rx_msg.len is only reset on RXACKE/RXOVR or after a\ncompleted message (RXEND). The number of bytes received before RXEND is\ndecided by the remote CEC device (it sets EOM), not by the driver. A\npeer that keeps sending bytes without ending the message drives RXBR\nrepeatedly, pushing rx_msg.len past 16 and writing peer-controlled bytes\nout of bounds into the surrounding memory. This is reachable in normal\noperation once the driver has probed and receiving is enabled, from the\nIRQ thread, without any local privilege.\n\nThe length check in the CEC core runs on the consumer side, after the\nbyte has been stored, so it does not prevent the overflow. Bound the\nindex in the driver before the store, as the other platform CEC drivers\nalready do (e.g. tegra_cec), dropping the excess bytes of an overlong\nframe.\n\nFound by static analysis tool CodeQL.","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: stm32: prevent out-of-bounds write on RX overflow","id":"CVE-2026-89725","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":"lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()","id":"CVE-2026-89726"},"packages":[],"prev":{"headline":"media: vicodec: fix out-of-bounds write in FWHT encoder","id":"CVE-2026-89724"},"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 remote CEC peer can trigger an out-of-bounds write in the STM32 CEC driver, potentially leading to kernel memory corruption and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89725/"}