media: dvb-core: fix wrong reinitialization of ringbuffer on reopen
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 34731df288a5ffe4b0c396caf8cd24c6a710a222 · < cfd94642025e6f71c8f754bdec0800ee95e4f3dd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: dvb-core: fix wrong reinitialization of ringbuffer on reopen
dvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the DVR device. dvb_ringbuffer_init() calls init_waitqueue_head(), which reinitializes the waitqueue list head to empty.
Since dmxdev->dvr_buffer.queue is a shared waitqueue (all opens of the same DVR device share it), this orphans any existing waitqueue entries from io_uring poll or epoll, leaving them with stale prev/next pointers while the list head is reset to {self, self}.
The waitqueue and spinlock in dvr_buffer are already properly initialized once in dvb_dmxdev_init(). The open path only needs to reset the buffer data pointer, size, and read/write positions.
Replace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct assignment of data/size and a call to dvb_ringbuffer_reset(), which properly resets pread, pwrite, and error with correct memory ordering without touching the waitqueue or spinlock.
From the CVE record · Linux
The Linux kernel’s dvb-core DVR open path reinitializes a waitqueue shared by all opens of the same DVR device. If a new reader opens the device while an io_uring poll or epoll wait is registered, the existing waitqueue entries are orphaned and left with stale pointers. This requires access to the DVR device; the input does not specify authentication requirements.
Engineers running Linux kernels with dvb-core DVR devices should check their kernel versions; affected versions are not specified.