---
title: "CVE-2026-89894: Linux kernel cx231xx - Out-of-Bounds Write"
description: "Linux kernel media cx231xx contains a heap out-of-bounds write caused by allowing geometry changes while the VBI queue is busy, letting attackers cause memory corruption, exploit requires running VBI stream."
url: https://panop.io/threat-heartbeat/CVE-2026-89894/
---

# CVE-2026-89894 Linux kernel cx231xx - Out-of-Bounds Write

Linux kernel media cx231xx contains a heap out-of-bounds write caused by allowing geometry changes while the VBI queue is busy, letting attackers cause memory corruption, exploit requires running VBI stream.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.16% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89894)

## Details

Type

Out-of-Bounds Write

Impact

Data Tampering

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

16 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for cx231xx VBI queue geometry handling.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89894](https://nvd.nist.gov/vuln/detail/CVE-2026-89894)
- [https://git.kernel.org/stable/c/a5dd3d7fba358ff9486f3f51b2a9038348c0970a](https://git.kernel.org/stable/c/a5dd3d7fba358ff9486f3f51b2a9038348c0970a)
- [https://git.kernel.org/stable/c/a636c72c7f522d984fa498fc0631f33a2d0be3fd](https://git.kernel.org/stable/c/a636c72c7f522d984fa498fc0631f33a2d0be3fd)
- [https://git.kernel.org/stable/c/aa3314506deb9703bcf0e889db08959440228fbf](https://git.kernel.org/stable/c/aa3314506deb9703bcf0e889db08959440228fbf)
- [https://git.kernel.org/stable/c/1d1079db8d1807e259a1d2679ed314949797aad9](https://git.kernel.org/stable/c/1d1079db8d1807e259a1d2679ed314949797aad9)
- [https://git.kernel.org/stable/c/54ac6df8b8d97eddc3ae97fd2045bdedc8541b6d](https://git.kernel.org/stable/c/54ac6df8b8d97eddc3ae97fd2045bdedc8541b6d)
- [https://git.kernel.org/stable/c/627a121c15fe05a541f44d86016294b80bada75d](https://git.kernel.org/stable/c/627a121c15fe05a541f44d86016294b80bada75d)
- [https://git.kernel.org/stable/c/7087bef6510c7df5df0b19192633b8ecc0f33a6f](https://git.kernel.org/stable/c/7087bef6510c7df5df0b19192633b8ecc0f33a6f)
- [https://git.kernel.org/stable/c/90d50648af36a1fbf5dbc99238de6fd0e58a13e0](https://git.kernel.org/stable/c/90d50648af36a1fbf5dbc99238de6fd0e58a13e0)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
