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.
CVSS
7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
34731df288a5ffe4b0c396caf8cd24c6a710a222 builds before 527cfa8a3486b3555c5c15e2f62be484a11398dc; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before fb378cf89be434ed1f10ab79cc4788fba8ae868d; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before f1e520ca2e83ece6731af6167c9e5e16931ecba0; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before af050ab44fa1b1897a940d7d756e512232f5e5df; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before d71781bad59b1c9d60d7068004581f9bf19c0c9d; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before cfd94642025e6f71c8f754bdec0800ee95e4f3dd; 34731df288a5ffe4b0c396caf8cd24c6a710a222 builds before 32eb8e4adc207ef31bc6e5ae56bab940b0176066; from 34731df288a5ffe4b0c396caf8cd24c6a710a222 before bfbc0b5b32a8f28ce284add619bf226716a59bc0
from 2.6.17 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.77; from 6.13 before 6.18.17; from 6.19 before 6.19.7; 7.0
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.