{"api_version":"1","generated_at":"2026-09-12T05:51:52+00:00","cve":"CVE-2026-89725","urls":{"html":"https://cve.report/CVE-2026-89725","api":"https://cve.report/api/cve/CVE-2026-89725.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89725","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89725"},"summary":{"title":"media: cec: stm32: prevent out-of-bounds write on RX overflow","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->rx_msg.msg[cec->rx_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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:20:02","updated_at":"2026-09-11 20:20:02"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035","name":"https://git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0c260d3f97e52978a8c769bb095ac0901333a3ac","name":"https://git.kernel.org/stable/c/0c260d3f97e52978a8c769bb095ac0901333a3ac","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57","name":"https://git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1","name":"https://git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89725","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89725","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d69ae57453c80a2193bcdb3fd762efbec447eecf c3edd7fb8e3692423a702705509947fc9c30b3d1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d69ae57453c80a2193bcdb3fd762efbec447eecf 0c260d3f97e52978a8c769bb095ac0901333a3ac git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d69ae57453c80a2193bcdb3fd762efbec447eecf a85ce3b175615c2e13bc01e8a1b6b6b6910fde57 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d69ae57453c80a2193bcdb3fd762efbec447eecf fb9dda38d4b9e90db07ed9a0ee2d35bf85494035 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.13","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.13 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/media/cec/platform/stm32/stm32-cec.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c3edd7fb8e3692423a702705509947fc9c30b3d1","status":"affected","version":"d69ae57453c80a2193bcdb3fd762efbec447eecf","versionType":"git"},{"lessThan":"0c260d3f97e52978a8c769bb095ac0901333a3ac","status":"affected","version":"d69ae57453c80a2193bcdb3fd762efbec447eecf","versionType":"git"},{"lessThan":"a85ce3b175615c2e13bc01e8a1b6b6b6910fde57","status":"affected","version":"d69ae57453c80a2193bcdb3fd762efbec447eecf","versionType":"git"},{"lessThan":"fb9dda38d4b9e90db07ed9a0ee2d35bf85494035","status":"affected","version":"d69ae57453c80a2193bcdb3fd762efbec447eecf","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/media/cec/platform/stm32/stm32-cec.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.13"},{"lessThan":"4.13","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"4.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"4.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"4.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"4.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->rx_msg.msg[cec->rx_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."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:46:36.679Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1"},{"url":"https://git.kernel.org/stable/c/0c260d3f97e52978a8c769bb095ac0901333a3ac"},{"url":"https://git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57"},{"url":"https://git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035"}],"title":"media: cec: stm32: prevent out-of-bounds write on RX overflow","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89725","datePublished":"2026-09-11T19:46:36.679Z","dateReserved":"2026-09-11T19:38:34.759Z","dateUpdated":"2026-09-11T19:46:36.679Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:20:02","lastModifiedDate":"2026-09-11 20:20:02","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89725","Ordinal":"1","Title":"media: cec: stm32: prevent out-of-bounds write on RX overflow","CVE":"CVE-2026-89725","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89725","Ordinal":"1","NoteData":"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->rx_msg.msg[cec->rx_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.","Type":"Description","Title":"media: cec: stm32: prevent out-of-bounds write on RX overflow"}]}}}