CVE-2026-23253
Last modified
CVE-2026-23253 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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(). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.17, < 5.10.253 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.203 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.167 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.77 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.17 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.7 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23253?
How severe is CVE-2026-23253?
How do I fix CVE-2026-23253?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23248In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23249In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2325Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13, 1…6.5
- CVE-2026-23250In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23251In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23252In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23254In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23255In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23256In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23257In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23258In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23259In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23253?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
