CVE-2026-99511

published 19 Nov 2026 · updated 21 Nov 2026

media: cx23885: Fix use-after-free in cx23885_finidev due to race condition

4.1MediumCVSS 4.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 75016a992d9b03f5cc6df1414d1da35840d4feeb, Kernel 2344922abe2ad811003794092931bf454b556109, Kernel 4c28161c8893bf7a396bda1ba9d8fa6e528c1a21 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: media: cx23885: Fix use-after-free in cx23885_finidev due to race condition In cx23885_v4l2_dev_notify_init, &dev->cx25840_work is bound with cx23885_av_work_handler, and &dev->ir_rx_work and &dev->ir_tx_work are bound with cx23885_ir_rx_work_handler and cx23885_ir_tx_work_handler. cx23885_irq can schedule these works on system_wq when an AV_CORE interrupt is received, and the IR subdevice can also schedule the IR works from its interrupt service routine via the v4l2_device notify callback. If we remove the device, cx23885_finidev makes cleanup and the memory allocated for dev is released by kfree(dev), while the works mentioned above may still be pending or running. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | cx23885_irq | schedule_work(&dev->cx25840_work) cx23885_finidev | cx23885_input_fini(dev) | cx23885_ir_fini(dev) | cx23885_shutdown(dev) | free_irq(pci_dev->irq, dev) | pci_disable_device(pci_dev) | cx23885_dev_unregister(dev) | v4l2_device_unregister(v4l2_dev) | kfree(dev) | // dev is freed | | cx23885_av_work_handler | // use dev (use-after-free) Fix it by canceling the works after the IRQ handler that can schedule them has been stopped, and before proceeding with the remaining cleanup in cx23885_finidev. Note that the flush_work() calls in cx23885_input_ir_stop() do not close this race: they only wait for works that are already queued or running at that moment, they do not prevent the IRQ handler, which is still registered at that point, from scheduling the works again afterwards, and they are skipped entirely when dev->sd_ir is NULL. The cancel_work_sync() calls are therefore placed after free_irq(), the only point at which no new work can be scheduled.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29 <75016a992d9b03f5cc6df1414d1da35840d4feeb, >=e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29 <2344922abe2ad811003794092931bf454b556109, >=e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29 <4c28161c8893bf7a396bda1ba9d8fa6e528c1a21, >=e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29 <544b575ba44d566cfd4f82e3d8faee5db01addf5, =2.6.3675016a992d9b03f5cc6df1414d1da35840d4feeb, 2344922abe2ad811003794092931bf454b556109, 4c28161c8893bf7a396bda1ba9d8fa6e528c1a21, 544b575ba44d566cfd4f82e3d8faee5db01addf5
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=2.6.36 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99511 severity on Zeptric[![CVE-2026-99511](https://zeptric.io/badge/cve/CVE-2026-99511.svg)](https://zeptric.io/cve/CVE-2026-99511)