Menu

Star on GitHub · 3.2k

CVE-2026-23253

7.8 · HIGH

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 reade…

Published Mar 18, 2026EPSS 0.14%

Overview

CVE-2026-23253 is a high-severity vulnerability. It was published on March 18, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 to

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-23253?

CVE-2026-23253 is a high-severity vulnerability. It was published on March 18, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-23253?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-23253?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-23253?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-23253 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all