{"metadata": {"vulnerability": "CVE-2026-99468", "count": 10, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 5}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.417Z", "date_only": false, "value": "2026-09-25T10:25:14.417Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99468", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:18:01Z", "date_only": false, "value": "2026-11-19T15:18:01Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-X34R-QR77-HQ6X", "record": "GHSA-X34R-QR77-HQ6X", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:18:01.110Z", "date_only": false, "value": "2026-11-19T15:18:01.110", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99468", "record": "FKIE_CVE-2026-99468", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:18:01.110Z", "date_only": false, "value": "2026-11-19T15:18:01.110", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99468", "record": "FKIE_CVE-2026-99468", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:25Z", "date_only": false, "value": "2026-11-19T15:31:25Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-X34R-QR77-HQ6X", "record": "GHSA-X34R-QR77-HQ6X", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:25Z", "date_only": false, "value": "2026-11-19T15:31:25Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-X34R-QR77-HQ6X", "record": "GHSA-X34R-QR77-HQ6X", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:32:58.204Z", "date_only": false, "value": "2026-11-19T16:32:58.204213Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644065346451141", "record": "CVE-2026-99468", "field": "creation_timestamp", "uuid": "784886b8-d0af-4763-835b-1e8d4ecb7636", "content": "CVE-2026-99468 media: imx-jpeg: cancel timeout worker when streaming stops In the Linux kernel, the following vulnerability has been resolved:\nmedia: imx-jpeg: cancel timeout worker when streaming stops\nEach per-fd context ctx owns a delayed_work (ctx-&gt;task_timer, callbackmxc_jpeg_device_run_timeout) armed via schedule_delayed_work() at the endof mxc_jpeg_device_run() to recover a stalled encode/decode job. The onlyexisting cancellation is cancel_delayed_work() in the frame-done IRQhandler, which de-queues a pending work item but does not wait for acallback that has already started, and it only runs when a frame completes.\nWhen the fd is closed while a job is in flight (the frame-done IRQ has notfired yet), nothing syncs the worker before mxc_jpeg_release() frees ctxwith kfree() after v4l2_m2m_ctx_release(). A queued or executingmxc_jpeg_device_run_timeout() can then recover ctx throughcontainer_of(&amp;ctx-&gt;task_timer) and dereference it (ctx-&gt;mxc_jpeg,slot_data, dev_warn) after ctx has been freed.\nCancel the worker from mxc_jpeg_stop_streaming(). The cancel cannot livein mxc_jpeg_release(): mxc_jpeg_device_run() arms the timer while holdingonly hw_lock, not the mxc_jpeg-&gt;lock mutex that release holds, so a cancelin release could still race a concurrent mxc_jpeg_device_run() thatre-arms the timer afterwards. mxc_jpeg_stop_streaming() instead runs insidev4l2_m2m_ctx_release() -&gt; vb2_queue_release(), i.e. afterv4l2_m2m_cancel_job() has set TRANS_ABORT and waited for any in-flight jobto finish (so __v4l2_m2m_try_queue() will not queue and v4l2_m2m_try_run()will not run any further job for this context, which preventsmxc_jpeg_device_run() from re-arming the timer) and before the m2m contextis freed. cancel_delayed_work_sync() removes a pending work item and waitsfor a running callback, so the worker can no longer race with thesubsequent kfree(). The cancel is placed before the buffer-release loop soa concurrently running timeout callback cannot race with it over the samebuffers. If the frame-done IRQ canceled a still-pending timer, this cancelis a no-op; if the timeout callback has already started, it waits for thecallback to finish. The same mxc_jpeg_stop_streaming() call is alsoreached from VIDIOC_STREAMOFF, which drains the worker early, althoughSTREAMOFF itself does not free ctx -- the use-after-free arises onlywhen the fd is later closed.\nThis bug was found by static analysis.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99468https://git.kernel.org/stable/c/77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341https://git.kernel.org/stable/c/49a0623994a10d3d333d48c304f89d816495f332https://git.kernel.org/stable/c/9e393784a902bb4eb00a21e46d389a32c7ea61b0https://git.kernel.org/stable/c/78fdfbf117c409273eecbfa7a528ef42358a0e38#kernel #Linux#CVE_2026_99468#bot", "url": "https://infosec.exchange/users/cve/statuses/117644065346451141"}], "metrics": {"as_of": "2026-11-19T18:38:26.532Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 14132.106504, "hours": 3.92558514, "days": 0.1635660475, "min_seconds": 14132.106504, "max_seconds": 14132.106504, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:42:54.426Z", "date_only": false, "value": "2026-11-19T14:42:54.426Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99468", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-19T18:38:26.532Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
