{"id":"CVE-2026-89725","summary":"media: cec: stm32: prevent out-of-bounds write on RX overflow","details":"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 & 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.","modified":"2026-09-14T03:46:28.648317771Z","published":"2026-09-11T19:46:36.679Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89725.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0c260d3f97e52978a8c769bb095ac0901333a3ac"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89725.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89725"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"d69ae57453c80a2193bcdb3fd762efbec447eecf"},{"fixed":"c3edd7fb8e3692423a702705509947fc9c30b3d1"},{"fixed":"0c260d3f97e52978a8c769bb095ac0901333a3ac"},{"fixed":"a85ce3b175615c2e13bc01e8a1b6b6b6910fde57"},{"fixed":"fb9dda38d4b9e90db07ed9a0ee2d35bf85494035"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89725.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.13.0"},{"fixed":"6.12.109"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.50"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.2.4"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89725.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}