media: dvb-core: fix wrong reinitialization of ringbuffer on reopen
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in 527cfa8a3486b3555c5c15e2f62be484a11398dc; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in fb378cf89be434ed1f10ab79cc4788fba8ae868d; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in f1e520ca2e83ece6731af6167c9e5e16931ecba0; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in af050ab44fa1b1897a940d7d756e512232f5e5df; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in d71781bad59b1c9d60d7068004581f9bf19c0c9d; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in cfd94642025e6f71c8f754bdec0800ee95e4f3dd; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in 32eb8e4adc207ef31bc6e5ae56bab940b0176066; From 34731df288a5ffe4b0c396caf8cd24c6a710a222 · fixed in bfbc0b5b32a8f28ce284add619bf226716a59bc0
- Linux Linux
2.6.17
- KernelLinux
From 2.6.17 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.77; From 6.13.0 · fixed in 6.18.17; From 6.19.0 · fixed in 6.19.7
References 8
git.kernel.org
- stable/c/527cfa8a3486b3555c5c15e2f62be484a11398dc
- stable/c/fb378cf89be434ed1f10ab79cc4788fba8ae868d
- stable/c/f1e520ca2e83ece6731af6167c9e5e16931ecba0
- stable/c/af050ab44fa1b1897a940d7d756e512232f5e5df
- stable/c/d71781bad59b1c9d60d7068004581f9bf19c0c9d
- stable/c/cfd94642025e6f71c8f754bdec0800ee95e4f3dd
- stable/c/32eb8e4adc207ef31bc6e5ae56bab940b0176066
- stable/c/bfbc0b5b32a8f28ce284add619bf226716a59bc0