Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89725, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < f2499b720ea9b874d58770885c6c2e8445a8c3ef
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < 3df1a4026662121011187247897fe95fd84e8a3a
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < 1b4fdefd788db990d1805feb5c7b2388de791ecd
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < c3edd7fb8e3692423a702705509947fc9c30b3d1
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < 0c260d3f97e52978a8c769bb095ac0901333a3ac
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < a85ce3b175615c2e13bc01e8a1b6b6b6910fde57
    • affected d69ae57453c80a2193bcdb3fd762efbec447eecf – < fb9dda38d4b9e90db07ed9a0ee2d35bf85494035
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89725 badge
[![CVE-2026-89725](https://cveledger.app/badge/CVE-2026-89725.svg)](https://cveledger.app/cve/CVE-2026-89725)

Record last updated .