PoC Monitor
← All CVEs
CVE-2026-89725published 11 Sep 2026 19:46 UTCData: JSON · API

Linux

media: cec: stm32: prevent out-of-bounds write on RX overflow

In the Linux kernel, the following vulnerability has been resolved: media: cec: stm32: prevent out-of-bounds write on RX overflow stm32_rx_done() appends each received CEC byte to rx_msg.msg[] using rx_msg.len as the write index, incrementing it on every RXBR (receive-byte-ready) interrupt without checking it against the buffer size: cec->rx_msg.msg[cec->rx_msg.len++] = val & 0xFF; rx_msg.msg[] is a fixed CEC_MAX_MSG_SIZE (16) byte array in struct cec_msg, and rx_msg.len is only reset on RXACKE/RXOVR or after a completed message (RXEND). The number of bytes received before RXEND is decided by the remote CEC device (it sets EOM), not by the driver. A peer that keeps sending bytes without ending the message drives RXBR repeatedly, pushing rx_msg.len past 16 and writing peer-controlled bytes out of bounds into the surrounding memory. This is reachable in normal operation once the driver has probed and receiving is enabled, from the IRQ thread, without any local privilege. The length check in the CEC core runs on the consumer side, after the byte has been stored, so it does not prevent the overflow. Bound the index in the driver before the store, as the other platform CEC drivers already do (e.g. tegra_cec), dropping the excess bytes of an overlong frame. Found by static analysis tool CodeQL.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < f2499b720ea9b874d58770885c6c2e8445a8c3ef
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < 3df1a4026662121011187247897fe95fd84e8a3a
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < 1b4fdefd788db990d1805feb5c7b2388de791ecd
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < c3edd7fb8e3692423a702705509947fc9c30b3d1
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < 0c260d3f97e52978a8c769bb095ac0901333a3ac
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < a85ce3b175615c2e13bc01e8a1b6b6b6910fde57
  • >= d69ae57453c80a2193bcdb3fd762efbec447eecf, < fb9dda38d4b9e90db07ed9a0ee2d35bf85494035

Fixed in f2499b720ea9b874d58770885c6c2e8445a8c3ef, 3df1a4026662121011187247897fe95fd84e8a3a, 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344, 1b4fdefd788db990d1805feb5c7b2388de791ecd, c3edd7fb8e3692423a702705509947fc9c30b3d1, 0c260d3f97e52978a8c769bb095ac0901333a3ac, a85ce3b175615c2e13bc01e8a1b6b6b6910fde57, fb9dda38d4b9e90db07ed9a0ee2d35bf85494035

Linux Linux
  • 4.13

Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to f2499b720ea9b874d58770885c6c2e8445a8c3ef or 3df1a4026662121011187247897fe95fd84e8a3a or 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344 or 1b4fdefd788db990d1805feb5c7b2388de791ecd or c3edd7fb8e3692423a702705509947fc9c30b3d1 or 0c260d3f97e52978a8c769bb095ac0901333a3ac or a85ce3b175615c2e13bc01e8a1b6b6b6910fde57 or fb9dda38d4b9e90db07ed9a0ee2d35bf85494035 or later.

Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.