FKIE_CVE-2026-99511

Vulnerability from fkie_nvd - Published: 2026-11-19 15:18 - Updated: 2026-11-19 15:18
Severity
Summary
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.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/pci/cx23885/cx23885-core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4c28161c8893bf7a396bda1ba9d8fa6e528c1a21",
              "status": "affected",
              "version": "e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29",
              "versionType": "git"
            },
            {
              "lessThan": "2344922abe2ad811003794092931bf454b556109",
              "status": "affected",
              "version": "e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29",
              "versionType": "git"
            },
            {
              "lessThan": "544b575ba44d566cfd4f82e3d8faee5db01addf5",
              "status": "affected",
              "version": "e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29",
              "versionType": "git"
            },
            {
              "lessThan": "75016a992d9b03f5cc6df1414d1da35840d4feeb",
              "status": "affected",
              "version": "e5514f104d875b3d28cbcd5d4f2b96ab2fca1e29",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/pci/cx23885/cx23885-core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.36"
            },
            {
              "lessThan": "2.6.36",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.117",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.61",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: cx23885: Fix use-after-free in cx23885_finidev due to race condition\n\nIn cx23885_v4l2_dev_notify_init, \u0026dev-\u003ecx25840_work is bound with\ncx23885_av_work_handler, and \u0026dev-\u003eir_rx_work and \u0026dev-\u003eir_tx_work\nare bound with cx23885_ir_rx_work_handler and\ncx23885_ir_tx_work_handler. cx23885_irq can schedule these works on\nsystem_wq when an AV_CORE interrupt is received, and the IR subdevice\ncan also schedule the IR works from its interrupt service routine via\nthe v4l2_device notify callback.\n\nIf we remove the device, cx23885_finidev makes cleanup and the memory\nallocated for dev is released by kfree(dev), while the works mentioned\nabove may still be pending or running. The sequence of operations that\nmay lead to a UAF bug is as follows:\n\nCPU0                                      CPU1\n\n                                          | cx23885_irq\n                                          | schedule_work(\u0026dev-\u003ecx25840_work)\ncx23885_finidev                           |\ncx23885_input_fini(dev)                   |\ncx23885_ir_fini(dev)                      |\ncx23885_shutdown(dev)                     |\nfree_irq(pci_dev-\u003eirq, dev)               |\npci_disable_device(pci_dev)               |\ncx23885_dev_unregister(dev)               |\nv4l2_device_unregister(v4l2_dev)          |\nkfree(dev)                                |\n// dev is freed                           |\n                                          | cx23885_av_work_handler\n                                          | // use dev (use-after-free)\n\nFix it by canceling the works after the IRQ handler that can schedule\nthem has been stopped, and before proceeding with the remaining\ncleanup in cx23885_finidev.\n\nNote that the flush_work() calls in cx23885_input_ir_stop() do not\nclose this race: they only wait for works that are already queued or\nrunning at that moment, they do not prevent the IRQ handler, which is\nstill registered at that point, from scheduling the works again\nafterwards, and they are skipped entirely when dev-\u003esd_ir is NULL.\nThe cancel_work_sync() calls are therefore placed after free_irq(),\nthe only point at which no new work can be scheduled."
    }
  ],
  "id": "CVE-2026-99511",
  "lastModified": "2026-11-19T15:18:06.480",
  "metrics": {},
  "published": "2026-11-19T15:18:06.480",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2344922abe2ad811003794092931bf454b556109"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4c28161c8893bf7a396bda1ba9d8fa6e528c1a21"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/544b575ba44d566cfd4f82e3d8faee5db01addf5"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/75016a992d9b03f5cc6df1414d1da35840d4feeb"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.