CVE-2026-23253

media: dvb-core: fix wrong reinitialization of ringbuffer on reopen

HIGH
7.8
CVSS Score
Published: March 18, 2026 at 05:01 PM UTC
Updated: October 19, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.17 ≤ v < 5.10.2535.11 ≤ v < 5.15.2035.16 ≤ v < 6.1.1676.13 ≤ v < 6.18.176.19 ≤ v < 6.19.76.2 ≤ v < 6.6.1306.7 ≤ v < 6.12.7734731df288a5ffe4b0c396caf8cd24c6a710a2227.07.0 rc1
Vendor states this is fixed in 32eb8e4adc207ef31bc6e5ae56bab940b0176066 (fixed)
Vendor states this is fixed in 527cfa8a3486b3555c5c15e2f62be484a11398dc (fixed)
Vendor states this is fixed in af050ab44fa1b1897a940d7d756e512232f5e5df (fixed)
Vendor states this is fixed in bfbc0b5b32a8f28ce284add619bf226716a59bc0 (fixed)
Vendor states this is fixed in cfd94642025e6f71c8f754bdec0800ee95e4f3dd (fixed)
Vendor states this is fixed in d71781bad59b1c9d60d7068004581f9bf19c0c9d (fixed)
Vendor states this is fixed in f1e520ca2e83ece6731af6167c9e5e16931ecba0 (fixed)
Vendor states this is fixed in fb378cf89be434ed1f10ab79cc4788fba8ae868d (fixed)
Vendor states this is fixed in 2.6.17 (unaffected)
Vendor states this is fixed in 5.10.253 (unaffected)
Vendor states this is fixed in 5.15.203 (unaffected)
Vendor states this is fixed in 6.1.167 (unaffected)
Vendor states this is fixed in 6.12.77 (unaffected)
Vendor states this is fixed in 6.18.17 (unaffected)
Vendor states this is fixed in 6.19.7 (unaffected)
Vendor states this is fixed in 6.6.130 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-665

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card