CVE-2026-23253
HIGHDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 3% of all known CVEs.
References
Related Vulnerabilities
Other CWE-665 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-0847 | High | 7.8 | 93% | KEV | Fix |
| CVE-2022-22719 | High | 7.5 | 69% | - | Fix |
| CVE-2020-28019 | High | 7.5 | 62% | - | Fix |
| CVE-2022-46164 | Critical | 9.4 | 47% | - | Fix |
| CVE-2022-37128 | Critical | 9.8 | 22% | - | - |
| CVE-2019-14271 | Critical | 9.8 | 19% | - | Fix |
Common questions
How do I fix CVE-2026-23253?
Published advisories record a fix for 270 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-23253 being actively exploited?
Not that we know of. CVE-2026-23253 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.14% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.
How severe is CVE-2026-23253?
CVE-2026-23253 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-23253 affect?
Published advisories record a fix for linux (Debian), aws (Ubuntu), aws-6.8 (Ubuntu), aws-hwe (Ubuntu), and 266 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-23253
Markdown
[](https://tridentstack.com/cve/CVE-2026-23253)HTML
<a href="https://tridentstack.com/cve/CVE-2026-23253"><img src="https://tridentstack.com/cve/badge/CVE-2026-23253.svg" alt="CVE-2026-23253"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-19.