HIGH Introduced in 5.5
cx231xx VbiQueue OOB
CVE-2026-89894
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.8HIGH
01Description
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.
02KernelScan AI Analysis
Risk summary
A local user with access to V4L2 device nodes on a system with a cx231xx USB video capture device can trigger a heap out-of-bounds write by changing the video format or standard while VBI streaming is active. The write offset is attacker-controlled and the corruption occurs in kernel heap memory, enabling potential privilege escalation or system crash. Systems without this specific USB hardware or without accessible device nodes are not affected.
Vulnerability analysis
The cx231xx USB video capture driver allows an application to change the capture format or video standard through the video device node while VBI streaming is active on the VBI node, because the busy-state check only guards the video queue. Since VBI buffers are sized from the original geometry but the URB completion handler copies data using updated geometry into a buffer allocated with old geometry, enlarging the width or switching standards mid-stream causes the handler to write past the end of the already-allocated VBI plane — a heap out-of-bounds write with an attacker-chosen offset. The fix rejects format and standard changes whenever either the video or VBI queue is busy, preventing the geometry from changing underneath an allocated buffer. Exploitation requires a cx231xx USB video capture device to be present and a local user with access to the V4L2 device nodes.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.10 | 5.5 | 5.10.270 | aa3314506deb |
| 5.15 | 5.5 | 5.15.221 | 90d50648af36 |
| 6.1 | 5.5 | 6.1.188 | a5dd3d7fba35 |
| 6.12 | 5.5 | 6.12.110 | 1d1079db8d18 |
| 6.18 | 5.5 | 6.18.51 | 7087bef6510c |
| 6.6 | 5.5 | 6.6.157 | 54ac6df8b8d9 |
| 7.2 | 5.5 | 7.2.5 | a636c72c7f52 |
| mainline | 5.5 | 7.3 | 627a121c15fe |
| cip/5.10 | 5.5 | 5.10.271-cip78 | aa3314506deb |
| cip/6.1 | 5.5 | 6.1.189-cip61 | a5dd3d7fba35 |
| cip/6.1-rt | 5.5 | 6.1.189-cip61-rt32 | a5dd3d7fba35 |
| cip/6.12 | 5.5 | 6.12.111-cip32 | 1d1079db8d18 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.111-cip32 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |
| cip/5.10 | Fixed in 5.10.271-cip78 |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.268-cip77-rt34) |