CVE-2026-89725: media: cec: stm32: prevent out-of-bounds write on RX overflow
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0c260d3f97e52978a8c769bb095ac0901333a3ac, 1b4fdefd788db990d1805feb5c7b2388de791ecd, 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0c260d3f97e52978a8c769bb095ac0901333a3ac, 1b4fdefd788db990d1805feb5c7b2388de791ecd, 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before f2499b720ea9b874d58770885c6c2e8445a8c3efaffected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before 3df1a4026662121011187247897fe95fd84e8a3aaffected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344affected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before 1b4fdefd788db990d1805feb5c7b2388de791ecdaffected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before c3edd7fb8e3692423a702705509947fc9c30b3d1affected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before 0c260d3f97e52978a8c769bb095ac0901333a3acaffected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before a85ce3b175615c2e13bc01e8a1b6b6b6910fde57affected · git
- d69ae57453c80a2193bcdb3fd762efbec447eecf and later · before fb9dda38d4b9e90db07ed9a0ee2d35bf85494035affected · git
- before 4.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89723Sep 11, 2026 · nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation31Monitor
- ← EarlierCVE-2026-89724Sep 11, 2026 · media: vicodec: fix out-of-bounds write in FWHT encoder31Monitor
- Later →CVE-2026-89726Sep 11, 2026 · lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c260d3f97e52978a8c769bb095ac0901333a3ac | Vendor (CNA) |
| Linux Linux | 1b4fdefd788db990d1805feb5c7b2388de791ecd | Vendor (CNA) |
| Linux Linux | 37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344 | Vendor (CNA) |
| Linux Linux | 3df1a4026662121011187247897fe95fd84e8a3a | Vendor (CNA) |
| Linux Linux | a85ce3b175615c2e13bc01e8a1b6b6b6910fde57 | Vendor (CNA) |
| Linux Linux | c3edd7fb8e3692423a702705509947fc9c30b3d1 | Vendor (CNA) |
| Linux Linux | f2499b720ea9b874d58770885c6c2e8445a8c3ef | Vendor (CNA) |
| Linux Linux | fb9dda38d4b9e90db07ed9a0ee2d35bf85494035 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1b4fdefd788db990d1805feb5c7b2388de791ecd
- git.kernel.org/stable/c/37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344
- git.kernel.org/stable/c/3df1a4026662121011187247897fe95fd84e8a3a
- git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57
- git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1
- git.kernel.org/stable/c/f2499b720ea9b874d58770885c6c2e8445a8c3ef
- git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035
Vendor advisories and official records. Exploit/PoC links are deliberately left out.