CVE-2026-89894media: cx231xx: reject geometry changes while the VBI queue is busy
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: media: cx231xx: reject geometry changes while the VBI queue is busy vidioc_s_fmt_vid_cap() and vidioc_s_std() change the device-wide dev->width / dev->norm but only refuse the change when the *video* queue (dev->vidq) is busy. The VBI queue (dev->vbiq) shares that same geometry: cx231xx_init_vbi_isoc() latches dma_q->lines_per_field from dev->norm, the VBI videobuf2 plane is sized from dev->width / dev->norm in vbi_queue_setup() and vbi_buf_prepare(), and cx231xx_do_vbi_copy() then recomputes the destination offset from the *live* dev->width and the latched lines_per_field on every URB completion: offset = lines_completed * (dev->width << 1) + ...; if (dma_q->current_field == 2) offset += dev->width * 2 * dma_q->lines_per_field; memcpy(plane + offset, p_buffer, lencopy); Because the VBI node shares video_ioctl_ops with the video node, an application can size a small VBI plane (REQBUFS/QBUF with a small width, or with the NTSC standard), then enlarge dev->width (or switch dev->norm to PAL) through the video node while the VBI stream is running -- the change is allowed because only dev->vidq is checked -- and let the device deliver a field-2 VBI payload. cx231xx_do_vbi_copy() now computes the offset with the larger geometry and memcpy()s past the end of the smaller plane that was already allocated, a heap out-of-bounds write whose offset is attacker-chosen and whose contents come from the device. The per-field guard in cx231xx_copy_vbi_line() does not help: it bounds the copy against the latched lines_per_field, not the plane's real capacity, and vb2 does not re-run buf_prepare() for an already prepared buffer. Refuse the format/standard change when the VBI queue is busy as well, so the geometry cannot change underneath an allocated VBI buffer.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < aa3314506deb9703bcf0e889db08959440228fbf
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < 90d50648af36a1fbf5dbc99238de6fd0e58a13e0
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < a5dd3d7fba358ff9486f3f51b2a9038348c0970a
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < 54ac6df8b8d97eddc3ae97fd2045bdedc8541b6d
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < 1d1079db8d1807e259a1d2679ed314949797aad9
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < 7087bef6510c7df5df0b19192633b8ecc0f33a6f
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < a636c72c7f522d984fa498fc0631f33a2d0be3fd
- affected 7c617138b8254a6bb60bfb5b8fc53eb8b3d6c3ab – < 627a121c15fe05a541f44d86016294b80bada75d
- affected 5.5
- unaffected < 5.5
- 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.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/aa3314506deb9703bcf0e889db08959440228fbf (opens in a new tab)
- https://git.kernel.org/stable/c/90d50648af36a1fbf5dbc99238de6fd0e58a13e0 (opens in a new tab)
- https://git.kernel.org/stable/c/a5dd3d7fba358ff9486f3f51b2a9038348c0970a (opens in a new tab)
- https://git.kernel.org/stable/c/54ac6df8b8d97eddc3ae97fd2045bdedc8541b6d (opens in a new tab)
- https://git.kernel.org/stable/c/1d1079db8d1807e259a1d2679ed314949797aad9 (opens in a new tab)
- https://git.kernel.org/stable/c/7087bef6510c7df5df0b19192633b8ecc0f33a6f (opens in a new tab)
- https://git.kernel.org/stable/c/a636c72c7f522d984fa498fc0631f33a2d0be3fd (opens in a new tab)
- https://git.kernel.org/stable/c/627a121c15fe05a541f44d86016294b80bada75d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80494 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89894)Record last updated .