Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1 dvb-core dvb_dvr_open initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1. It has been rated as critical. Affected by this issue is the function dvb_dvr_open of the component dvb-core. Performing a manipulation results in initialization. This vulnerability is identified as CVE-2026-23253. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1. This affects the function dvb_dvr_open of the component dvb-core. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-23253 since 01/13/2026. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/02/2026).

The vulnerability scanner Nessus provides a plugin with the ID 311783 (Debian dla-4561 : linux-config-6.1 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.77, 6.18.17, 6.19.7 or 7.0-rc2 eliminates this vulnerability. Applying the patch d71781bad59b1c9d60d7068004581f9bf19c0c9d/cfd94642025e6f71c8f754bdec0800ee95e4f3dd/32eb8e4adc207ef31bc6e5ae56bab940b0176066/bfbc0b5b32a8f28ce284add619bf226716a59bc0 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (311783) and CERT Bund (WID-SEC-2026-0790). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (Linux): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 311783
Nessus Name: Debian dla-4561 : linux-config-6.1 - security update

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.77/6.18.17/6.19.7/7.0-rc2
Patch: d71781bad59b1c9d60d7068004581f9bf19c0c9d/cfd94642025e6f71c8f754bdec0800ee95e4f3dd/32eb8e4adc207ef31bc6e5ae56bab940b0176066/bfbc0b5b32a8f28ce284add619bf226716a59bc0

Timelineinfo

01/13/2026 CVE reserved
03/18/2026 +64 days Advisory disclosed
03/18/2026 +0 days VulDB entry created
06/02/2026 +76 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23253 (🔒)
GCVE (CVE): GCVE-0-2026-23253
GCVE (VulDB): GCVE-100-351561
CERT Bund: WID-SEC-2026-0790 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 03/18/2026 19:39
Updated: 06/02/2026 14:49
Changes: 03/18/2026 19:39 (59), 03/19/2026 19:26 (7), 03/24/2026 17:52 (1), 05/03/2026 18:48 (2), 06/02/2026 14:49 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!